The commits for each project will always be a seperate mailing list from the dev discussion list and each project will have it's own commits list.

As for the name, the change that Ted proposes is ok, i.e. putting the project name first to enable nicer sorting.


On Mar 13, 2006, at 2:30 PM, Ted Leung wrote:

Philippe Bossut wrote:
Pieter Hartsook wrote:
Would it make more sense to include the commits list in with the other
lists per project, ie. the cosmo-commits would group with cosmo-dev,
etc.

Rather than lumping all the commits together?


I like to keep the commits and discussion separated. I guess that some people may want to check the discussions without being annoyed by the commits. Not sure if it's standard in other OS projects but wx does this for instance.

FWIW, I filter commits and discussions in separate imap folders and review them separately and like to continue to do this easily.
I think what Pieter is asking for is the second option that I proposed: keep the commits lists separate, but change the naming so that the name of the project is first and not second. For mail readers that sort foldernames alphabetically, this puts the commits list with the project list instead of clustering all the commits lists together.
Is that right Pieter?

Ted
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general

---
Bear

Build and Release Engineer
Open Source Applications Foundation (OSAF)
[EMAIL PROTECTED]
http://www.osafoundation.org

[EMAIL PROTECTED]
http://code-bear.com

PGP Fingerprint = 9996 719F 973D B11B E111  D770 9331 E822 40B3 CD29


Attachment: PGP.sig
Description: This is a digitally signed message part

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general

Reply via email to