Good to hear from infrastructure@ ! We all agree that the svn lock/svn unlock traffic was a bad thing, and even worse that 2 mails were sent for each file in the repository. AFAIK this is result of changing a simple property in the tomcat repository ( for line ending ), and it's a serious bug in svn or how svn is configured to generate all this spam. I think the change made in tomcat is perfectly reasonable, and other projects may do similar things - I hope svn will be fixed, or maybe infrastructure can add some filters to drop such messages.
Costin On 7/20/06, Garrett Rooney <[EMAIL PROTECTED]> wrote:
So, I'm not entirely clear what the justification for all the 'svn lock'/'svn unlock' traffic from the Tomcat section of the Subversion repository was this morning, but I do know that judging from the files that were involved (uhh, all of them, I think), the log message (something about setting properties) and the fact that they were immediately unlocked, there's no reason it should have been done. That caused a ridiculous number of email notifications to be sent, filling the outbound mail queue for quite some time. Please don't ever do that again. There is almost no reason for locking files in our Subversion repository, and there is literally no reason for locking ALL the files in a given ASF project. -garrett, on behalf of the ASF Infrastructure team
