[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cp-patches] Re: [commit-cp] Reply-To set to classpath-patches
From: |
Michael Koch |
Subject: |
Re: [cp-patches] Re: [commit-cp] Reply-To set to classpath-patches |
Date: |
Wed, 12 Jan 2005 07:43:30 +0100 |
User-agent: |
KMail/1.7.1 |
Am Mittwoch, 12. Januar 2005 03:18 schrieb Archie Cobbs:
> Mark Wielaard wrote:
> > There are not many people actually reading commit-classpath since
> > it only carries (a large volume) of automatic emails (mainly from
> > cvs commits). Replies might not always be read by everybody
> > interested in a change. So I set the reply-to for this list to
> > address@hidden so discussion about patches really
> > happens on that list.
>
> Maybe it's just me, but I don't see much point in having separate
> lists for commit-classpath and classpath-patches. Seems like they
> have the same customers. Plus the volume of commit-classpath is
> strictly bounded by the volume of classpath-patches (because we
> require posts to the former before each commit) and so by only
> subscribing to classpath-patches you're only changing the amount of
> Classpath email you receive by a small constant factor (ie., <= 2).
>
> It's also seems a little silly to see posts to classpath-patches
> that say "I'm checking this in" with a patch followed immediately
> by the post to commit-classpath with the checkin and URLs to the
> exact same patch. If there were one list, the first email wouldn't
> be necessary.
>
> Just random complaints, it's not really annoying enough to actually
> do anything about it just yet :-)
I find it very useful to have both lists. People who don't need
commit-classpath are not forced to subscribe to it. I use
commit-classpath to check what patches got really commited to
classpath and which got forgot. This is really useful when merging
stuff to GCJ.
Michael
--
Homepage: http://www.worldforge.org/