I panicked a bit on the last message and while I still would like to
freeze SVN updates for a little while longer, I don't think the
situation is as bad as it seems. There are a couple of issues that
appear to be involved:
1. I was doing svn log against my local copy (which was current of
2007-01-25), however that intentionally does not show the log
messages of subsequent commits. If you do the appropriate svn log
command against the URL of the file (for example, svn log https://
svn.apache.org/repos/asf/logging/log4j/trunk/tests/build.xml), you
will see the log messages for Elias' recent commits.
2. I'm guessing that the commit emails were generated by SVN but
rejected by the log4j-dev list since they appeared to come from an
non-subscriber. Elias and the list moderator (more about that in the
next point) may have gotten a notice of the rejection. Elias please
check if you got rejection notices from log4j-dev. If so, please
subscribe to log4j-dev as [EMAIL PROTECTED] and if the rejection
notices still have the body of the commit notice, please forward them
to the list (ideally as [EMAIL PROTECTED] to make sure that that
address gets through the subscriber-only filter).
3. [EMAIL PROTECTED] is directed to defunct email
address of a person that does not appear to be currently involved
with log4j. So if there were moderation notices on the recent svn
commits they didn't go to anyone.
4. All my attempts to administer log4j-dev appear to be blocked and
I'll take that up with infrastructure.
While I appreciate Elias' effort, the flurry of changes is a bit
overwhelming to follow especially when the normal notification
process is broken. It is going to a little while to process the
recent changes.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
