Crossfire Mailing List Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Mailing list redo.
- To:
- Subject: Re: Mailing list redo.
- From: Bob Tanner
- Date: Sat, 17 Jun 2000 00:42:42 -0500
- In-Reply-To: <>; from on Fri, Jun 16, 2000 at 09:53:28PM -0700
- Mail-Followup-To:
- References: <>
- User-Agent: Mutt/1.2i
Quoting Mark Wedel ():
> crossfire-announce: For announcement of new versions. Not that frequently
> used. Moderated list in which only I (or the tanners) can send mail out on.
>
> crossfire-cvs: Messages about updates to the cvs repository. This can be
> useful for people running servers who want to see what may have changed to
> determine if they do an update, but don't want all the discussion. Also, it
> would be very easy to modify the cvs repository so all commits are automatically
> sent to this list (the info on them), which might be another reason to keep it
> seperate. Peter - I can provide the details on how to do that.
I sent similar info to Peter with a perl script we use internall for posting
commits made to our cvs server.
> crossfire-developers: More technical list about the
> developement/programming of crossfire. Discussion of creation of maps
> would also apply here. bugs would also be sent to this list. This could
> potentially be subdievided further (probably down the road) based on maps,
> client, server, editor, and any other major pieces.
I did crossfire-devel, that ok? I also went on your first email and did
crossfire-devel, but not crossfire-cvs and ask Peter to forward commits to
crossfire-devel.
--
Bob Tanner <> | Phone : (952)943-8700
http://www.mn-linux.org | Fax : (952)943-8500
Key fingerprint = 6C E9 51 4F D5 3E 4C 66 62 A9 10 E5 35 85 39 D9