I found it easy to delete via filtering for "svn lock" and "svn unlock".
It's different for the archives, but for them this traffic peak will not
be serious. The worst thing was, that mails got delayed by several hours.
I would prefer to keep svn commits on the dev list.
Yoav Shapira 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]
--
kippdata informationstechnologie GmbH
Bornheimer Str. 33a
53111 Bonn
Tel.: 0228/98549-0
Fax: 0228/98549-50
www.kippdata.de
=======================
kippdata informationstechnologie GmbH
Bornheimer Str. 33a
D-53111 Bonn
Tel.: +49/0228/98549-0
Fax: +49/0228/98549-50
www.kippdata.de
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
