You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@logging.apache.org by Mark Womack <mw...@apache.org> on 2005/10/12 19:20:53 UTC
SVN Commit Email Messages
Henri,
It appears that all svn commit messages for every repository are being
routed to general@logging.apache.org instead of the subproject specific
email lists (eg logging-log4j-cvs@apache.org, etc).
Also, we'd like to possibly change/create new email lists for this purpose,
more along the lines of log4j-commit@logging.apache.org, etc. What do we
need to do for this? Should we send a different request to infrastructure
to set these up?
thanks,
-Mark
Re: SVN Commit Email Messages
Posted by Henri Yandell <ba...@apache.org>.
Yep, you hook a path in the system to a mailing list. Take a look at the
asf-mailer.conf file. Once you get passed the initial noise, it becomes
pretty repititous, though the suppress-if-any option takes a bit of
getting used to.
There are various tricks to make the hooking easier, ie) using a wildcard
to automatically get the hook in place for all subprojects, but it hits
problems when things don't follow a simple pattern.
Hen
On Mon, 17 Oct 2005, Mark Womack wrote:
> Reposting this to include Henri. I don't think he got the original post.
>
> Is it possible to connect subdirs of a repo to different mailing lists? If
> so, we can create the subdirs like we want them in the sandbox and then
> connect the mailint lists...
>
> -Mark
>
> ----- Original Message ----- From: "Curt Arnold" <ca...@apache.org>
> To: "Logging General" <ge...@logging.apache.org>
> Sent: Wednesday, October 12, 2005 12:22 PM
> Subject: Re: SVN Commit Email Messages
>
>
>>
>> On Oct 12, 2005, at 1:18 PM, Henri Yandell wrote:
>>
>>>
>>> Oops, my reply this morning must have failed due to being the wrong email
>>> address.
>>>
>>> I screwed up the email setup, and have committed a fix just now so it'll
>>> use the -cvs addresses that were used before. The sandbox might have
>>> problems; I need to test that.
>>>
>>> In terms of -cvs vs -commits; that'd be a separate request. Though much
>>> of the ASF is still on the -cvs's and I suspect that getting those
>>> changed will be a long task for somebody next year.
>>>
>>> Hen
>>
>> I've suggested that sandbox be rearranged so that it is a overall logging
>> services playground and not just a set of unsupported appenders for log4j.
>> I haven't had a chance to fomulate a full proposal, but basically I'd
>> assume that there would eventually be a structure like:
>>
>> logging/
>> sandbox/
>> logj4/
>> contribs/ (previous logging-log4j/contribs)
>> sandbox/ (previous logging-sandbox)
>> trunk/
>> tags/
>> branches/
>> log4cxx/
>> log4net/
>> log4php/
>> strict-xml/ (example of non-sub product specific sandbox
>> project)
>>
>> If we had something like that, then it might be appropriate that all the
>> sub-project specific sandbox commits to go to the same list as the
>> subproject commits. That is any commits in logging/sandbox/log4j would go
>> to log4j-cvs@logging.apache.org, commits in logging/sandbox/ log4cxx would
>> go to log4cxx-cvs@logging.apache.org, etc. Commits that aren't associated
>> with an established subproject could go to general@logging.apache.org.
>>
>> If you'd like to create the log4j, log4cxx subdirs of logging/sandbox and
>> set up the commit messages, I could then later move the stuff underneath
>> them.
>>
>>
>
>
Re: SVN Commit Email Messages
Posted by Mark Womack <mw...@apache.org>.
Reposting this to include Henri. I don't think he got the original post.
Is it possible to connect subdirs of a repo to different mailing lists? If
so, we can create the subdirs like we want them in the sandbox and then
connect the mailint lists...
-Mark
----- Original Message -----
From: "Curt Arnold" <ca...@apache.org>
To: "Logging General" <ge...@logging.apache.org>
Sent: Wednesday, October 12, 2005 12:22 PM
Subject: Re: SVN Commit Email Messages
>
> On Oct 12, 2005, at 1:18 PM, Henri Yandell wrote:
>
>>
>> Oops, my reply this morning must have failed due to being the wrong
>> email address.
>>
>> I screwed up the email setup, and have committed a fix just now so it'll
>> use the -cvs addresses that were used before. The sandbox might have
>> problems; I need to test that.
>>
>> In terms of -cvs vs -commits; that'd be a separate request. Though much
>> of the ASF is still on the -cvs's and I suspect that getting those
>> changed will be a long task for somebody next year.
>>
>> Hen
>
> I've suggested that sandbox be rearranged so that it is a overall logging
> services playground and not just a set of unsupported appenders for
> log4j. I haven't had a chance to fomulate a full proposal, but basically
> I'd assume that there would eventually be a structure like:
>
> logging/
> sandbox/
> logj4/
> contribs/ (previous logging-log4j/contribs)
> sandbox/ (previous logging-sandbox)
> trunk/
> tags/
> branches/
> log4cxx/
> log4net/
> log4php/
> strict-xml/ (example of non-sub product specific sandbox
> project)
>
> If we had something like that, then it might be appropriate that all the
> sub-project specific sandbox commits to go to the same list as the
> subproject commits. That is any commits in logging/sandbox/log4j would
> go to log4j-cvs@logging.apache.org, commits in logging/sandbox/ log4cxx
> would go to log4cxx-cvs@logging.apache.org, etc. Commits that aren't
> associated with an established subproject could go to
> general@logging.apache.org.
>
> If you'd like to create the log4j, log4cxx subdirs of logging/sandbox and
> set up the commit messages, I could then later move the stuff underneath
> them.
>
>
Re: SVN Commit Email Messages
Posted by Curt Arnold <ca...@apache.org>.
On Oct 12, 2005, at 1:18 PM, Henri Yandell wrote:
>
> Oops, my reply this morning must have failed due to being the wrong
> email address.
>
> I screwed up the email setup, and have committed a fix just now so
> it'll use the -cvs addresses that were used before. The sandbox
> might have problems; I need to test that.
>
> In terms of -cvs vs -commits; that'd be a separate request. Though
> much of the ASF is still on the -cvs's and I suspect that getting
> those changed will be a long task for somebody next year.
>
> Hen
I've suggested that sandbox be rearranged so that it is a overall
logging services playground and not just a set of unsupported
appenders for log4j. I haven't had a chance to fomulate a full
proposal, but basically I'd assume that there would eventually be a
structure like:
logging/
sandbox/
logj4/
contribs/ (previous logging-log4j/contribs)
sandbox/ (previous logging-sandbox)
trunk/
tags/
branches/
log4cxx/
log4net/
log4php/
strict-xml/ (example of non-sub product specific sandbox
project)
If we had something like that, then it might be appropriate that all
the sub-project specific sandbox commits to go to the same list as
the subproject commits. That is any commits in logging/sandbox/log4j
would go to log4j-cvs@logging.apache.org, commits in logging/sandbox/
log4cxx would go to log4cxx-cvs@logging.apache.org, etc. Commits
that aren't associated with an established subproject could go to
general@logging.apache.org.
If you'd like to create the log4j, log4cxx subdirs of logging/sandbox
and set up the commit messages, I could then later move the stuff
underneath them.
Re: SVN Commit Email Messages
Posted by Henri Yandell <ba...@apache.org>.
Oops, my reply this morning must have failed due to being the wrong email
address.
I screwed up the email setup, and have committed a fix just now so it'll
use the -cvs addresses that were used before. The sandbox might have
problems; I need to test that.
In terms of -cvs vs -commits; that'd be a separate request. Though much of
the ASF is still on the -cvs's and I suspect that getting those changed
will be a long task for somebody next year.
Hen
On Wed, 12 Oct 2005, Mark Womack wrote:
> Henri,
>
> It appears that all svn commit messages for every repository are being routed
> to general@logging.apache.org instead of the subproject specific email lists
> (eg logging-log4j-cvs@apache.org, etc).
>
> Also, we'd like to possibly change/create new email lists for this purpose,
> more along the lines of log4j-commit@logging.apache.org, etc. What do we
> need to do for this? Should we send a different request to infrastructure to
> set these up?
>
> thanks,
> -Mark
>