I was talking about supressing svn lock/unlock. I don't think anyone cares about the internal svn behavior - locking or unlocking files, even setting properties.
About having a separate list - we had this discussion countless times before, having stuff on a list or another doesn't force anyone to read them, those who do want to read them will subscribe to a list ( or set a filter ) anyway, those who don't will also set a filter or ignore them. Costin On 7/20/06, Yoav Shapira <[EMAIL PROTECTED]> wrote:
Hi, On 7/20/06, Costin Manolache <[EMAIL PROTECTED]> wrote: > The svn messages are quite horrible IMO. Is there any way to suppress them > in future ? Some projects have a separate [svn|commits|cvs|[EMAIL PROTECTED] mailing list. We could do that, but then you can into the mode of reminding all committers to subscribe to those lists. Having stuff on the dev lists encourages all developers to look at commits, raising the inspection level a bit one would think. And honestly, people who want to filter these messages out can do so, whether they are on their own list or on this one. It's quite easy to create rules for them, including temporary filters like to handle today's unusual amount of messages. So all in all, let's treat today as the unusual event it was in terms of volume of SVN messages, and keep things the same unless people have strong objections. Yoav --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
