Nikodemus Siivola wrote:
For extra goodness those mailing lists could live under lists.common-lisp.net, so that we don't have to worry about clobbering the project namespace. OTOH, if all project based lists have foo- prefixes, this is really not an issue. (Just thinking out loud.)
I like the prefix better (from a sysadm standpoint). What about "np" as in "no project". So, "np-regex-coach@common-lisp.net", for instance. This precludes any project ever being named "np".
Erik.
I like the prefix better (from a sysadm standpoint). What about "np" as in "no project". So, "np-regex-coach@common-lisp.net", for instance. This precludes any project ever being named "np".
Suits me. Other, more verbose, but possibly less confusing prefix would be "list".
So list-regexr-coach@common-lisp.net etc.
Either is fine with me.
Cheers,
-- Nikodemus
Nikodemus Siivola tsiivola@cc.hut.fi writes:
I like the prefix better (from a sysadm standpoint). What about "np" as in "no project". So, "np-regex-coach@common-lisp.net", for instance. This precludes any project ever being named "np".
Suits me. Other, more verbose, but possibly less confusing prefix would be "list".
So list-regexr-coach@common-lisp.net etc.
Either is fine with me.
With me too. The only problem I see is what to do if the owner decides to host the project on c-l net? (this might not be probable in this case, but maybe in others).
How about just
regex-coach-{devel|announce|help}@common-lisp.net
just no project?
Regards, Mario.
-
Erik Enge -
Mario Mommer -
Nikodemus Siivola