You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Mladen Turk <mt...@apache.org> on 2006/07/20 13:51:00 UTC
SVN messages.
If anyone wonders what all those SVN commit messages are about,
they are about moving the /sandbox to the /sandbox/tomcat-lite
I choose the name, but I suppose Costing might have other ideas,
so a simple 'svn mv tomcat-lite what-ever-name' should do the trick.
The problems was because the /path/* can not be moved to the
/path/subdir/*, so thats how all those temp dirs were used.
Anyhow it will allow other committers to create something
inside /sandbox (BTW, The README.txt says it should be
/sandbox/component/trunk)
Regards,
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: SVN messages.
Posted by "William A. Rowe, Jr." <wr...@rowe-clan.net>.
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 unlocking are historical information. Next time it might
make sense to do an atomic operation?
Bill
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: SVN messages.
Posted by Yoav Shapira <yo...@apache.org>.
Hi,
On 7/20/06, Ian Darwin <ia...@darwinsys.com> 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 messages.
>
> That is the wrong answer:-) You are ignoring the anti-community
> effects of all that trash being sent over the internet - probably
> several gigabytes of traffic wasted in one day - as well as the costs to
> people who pay for bandwidth - filtering it is too late!
>
> 2400 messages at 2294 bytes * 500 subscribers is about 2.5GB of totally
> garbage network traffic sent out by the Apache mail server over a few
> hours (I don't know how many subscribers there are, that was just a
> guess). And that 2294 is a bit high as it includes the Received: lines
> that are added by sendmail, but still, it's a measurable amount of
> wasted bandwidth.
Yes, no one says it was good or effective or efficienct. All I was
saying is that it's a one-time thing, hopefully, so to change the
infrastructure because of it seems unwarranted. If someone really has
an itch to scratch here, go enhance SVN to lock entire trees in one
atomic operation ;)
Yoav
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: SVN messages.
Posted by Ian Darwin <ia...@darwinsys.com>.
> 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 anti-community
effects of all that trash being sent over the internet - probably
several gigabytes of traffic wasted in one day - as well as the costs to
people who pay for bandwidth - filtering it is too late!
2400 messages at 2294 bytes * 500 subscribers is about 2.5GB of totally
garbage network traffic sent out by the Apache mail server over a few
hours (I don't know how many subscribers there are, that was just a
guess). And that 2294 is a bit high as it includes the Received: lines
that are added by sendmail, but still, it's a measurable amount of
wasted bandwidth.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: SVN messages.
Posted by Mladen Turk <mt...@apache.org>.
Yoav Shapira wrote:
> Hi,
>
> On 7/20/06, Costin Manolache <co...@gmail.com> 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 unless people have
> strong objections.
>
I think we should investigate if there is chance to have
the lock/unlock messages removed from commit messages.
Since those are admin messages, they will be visible
anyhow if someone wishes to commit on a locked file,
and suppress potential future mail floods.
--
Mladen.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: SVN messages.
Posted by Andy Piper <an...@bea.com>.
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 "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 <co...@gmail.com> 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|similar]@projectname.apache.org 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: dev-unsubscribe@tomcat.apache.org
>>For additional commands, e-mail: dev-help@tomcat.apache.org
>
>--
>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: dev-unsubscribe@tomcat.apache.org
>For additional commands, e-mail: dev-help@tomcat.apache.org
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: SVN messages.
Posted by Rainer Jung <ra...@kippdata.de>.
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 <co...@gmail.com> 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|similar]@projectname.apache.org 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: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
--
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: SVN messages.
Posted by Costin Manolache <co...@gmail.com>.
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 <yo...@apache.org> wrote:
>
> Hi,
>
> On 7/20/06, Costin Manolache <co...@gmail.com> 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|similar]@projectname.apache.org 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: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
Re: SVN messages.
Posted by Yoav Shapira <yo...@apache.org>.
Hi,
On 7/20/06, Costin Manolache <co...@gmail.com> 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|similar]@projectname.apache.org 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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org
Re: SVN messages.
Posted by Costin Manolache <co...@gmail.com>.
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 that the move is done - don't want
to go over
another mail flood again :-)
Costin
On 7/20/06, Mladen Turk <mt...@apache.org> wrote:
>
> If anyone wonders what all those SVN commit messages are about,
> they are about moving the /sandbox to the /sandbox/tomcat-lite
> I choose the name, but I suppose Costing might have other ideas,
> so a simple 'svn mv tomcat-lite what-ever-name' should do the trick.
> The problems was because the /path/* can not be moved to the
> /path/subdir/*, so thats how all those temp dirs were used.
>
> Anyhow it will allow other committers to create something
> inside /sandbox (BTW, The README.txt says it should be
> /sandbox/component/trunk)
>
> Regards,
> Mladen.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
Re: SVN messages.
Posted by Martin van den Bemt <ml...@mvdb.net>.
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 anyone wonders what all those SVN commit messages are about,
> they are about moving the /sandbox to the /sandbox/tomcat-lite
> I choose the name, but I suppose Costing might have other ideas,
> so a simple 'svn mv tomcat-lite what-ever-name' should do the trick.
> The problems was because the /path/* can not be moved to the
> /path/subdir/*, so thats how all those temp dirs were used.
>
> Anyhow it will allow other committers to create something
> inside /sandbox (BTW, The README.txt says it should be
> /sandbox/component/trunk)
>
> Regards,
> Mladen.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: dev-help@tomcat.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org