Bit off topic, but couldn't stop thinking about it :)
Those mails are actually some kind of chaos theory proof. You being the butterfly flapping your
wings (typing some characters on the keyboard) and we all have witnessed what a flap of a wing can
cause :)
Mvgr,
Martin
Mladen Turk wrote:
If
Hi,
On 7/20/06, Ian Darwin <[EMAIL PROTECTED]> wrote:
> 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
Why is subscribing to two lists so hard? I expect that a significant
proportion of this list do not want the svn messages - and opt in
seems far more friendly than filter out.
Just my $0.02
andy
At 21:18 20/07/2006, Rainer Jung wrote:
I found it easy to delete via filtering for "svn lock" and
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.
That is the wrong answer:-) You are ignoring the an
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 ?
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 un
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
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:
Costin Manolache wrote:
The svn messages are quite horrible IMO. Is there any way to suppress them
in future ?
Yes - it's really this project's fault that you didn't adopt the suggestion
that dev@ discussion and commits@ notification don't belong on the same list ;-)
And No - locking and unloc
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
c
The svn messages are quite horrible IMO. Is there any way to suppress them
in future ?
Regarding the move - again, IMO it was not necessary, nothing prevented
creation of
a /sandbox/foo, and I think having a common java/ tree for components that
didn't want
separate tree was a good thing. But now
10 matches
Mail list logo
