__matthewHawthorne wrote:
gmane.org is great, that's how I access the apache mailing lists. A
good filtering technique is to mark all messages as read, except for
projects that you're interested in.
I apologize for going off topic, but has anyone experienced delays
when sending with gmane? My
gmane.org is great, that's how I access the apache mailing lists. A
good filtering technique is to mark all messages as read, except for
projects that you're interested in.
I apologize for going off topic, but has anyone experienced delays when
sending with gmane? My sent messages show up almo
Emmanuel Bourg wrote:
It seems some prefer to keep the commit messages in the list, and
others prefer a clean list with just the discussions. So what about
this :
- commons-dev : discussions + cvs messages
- commons-cvs : only the cvs messages
- commons-talk: only the discussions
or maybe easie
sense
of community and spirit..
Eric
> -Original Message-
> From: David Graham [mailto:[EMAIL PROTECTED]
> Sent: Thursday, October 30, 2003 3:02 PM
> To: Jakarta Commons Developers List
> Subject: Re: [all] new list for cvs commits? (was Re:
> commons-configuration)
>
--- Emmanuel Bourg <[EMAIL PROTECTED]> wrote:
> It seems some prefer to keep the commit messages in the list, and others
>
> prefer a clean list with just the discussions. So what about this :
>
> - commons-dev : discussions + cvs messages
> - commons-cvs : only the cvs messages
> - commons-talk
It seems some prefer to keep the commit messages in the list, and others
prefer a clean list with just the discussions. So what about this :
- commons-dev : discussions + cvs messages
- commons-cvs : only the cvs messages
- commons-talk: only the discussions
or maybe easier to set up :
- commons
I think the mailing list guidelines at
http://jakarta.apache.org/site/mail2.html#Commons could include at least
a warning like some other lists at Jakarta. Something like "Subscribers
to this list will also get notices of every CVS checkin of new or
changed code modules".
Emmanuel
smime.p7s
I agree that contributors should keep an eye on CVS commits, but a
separate list doesn't prevent them from doing so. That's less confusing
for newcomers like Hernan, reduce the noise for the non commiter folks
here just interested in the discussions, and makes the archive more
readable.
Emmanu
CVS commit messages here usually go to [EMAIL PROTECTED] That address is
directed to $project-dev@ because developers are expected to maintain
oversight of the CVS. The problem with Jakarta Commons is that all projects
are on one list. If there is too much traffic for a given subproject, a
separ
It makes sense for the commit messages to be delivered to the dev list
because they directly relate to the development of the project. The
problem with commons-dev is that many different projects use it so the
volume is higher than other dev lists. Simple email filtering rules help
to get rid of
10 matches
Mail list logo
