Date: Tue, 16 Jan 2001 17:40:58 -0500
Message-Id: <200101162240.RAA11637@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <3A64C2DF.FB6F6ED0@phekda.freeserve.co.uk> (message from Richard
	Dawe on Tue, 16 Jan 2001 21:53:35 +0000)
Subject: Re: Section for KB on DJGPP development (was 'contributing...')
References: <E14D7mG-0000ad-00 AT phekda DOT freeserve DOT co DOT uk> <3A637247 DOT ECA2ECBA AT phekda DOT freeserve DOT co DOT uk> <200101152228 DOT RAA00794 AT envy DOT delorie DOT com> <3A64C2DF DOT FB6F6ED0 AT phekda DOT freeserve DOT co DOT uk>
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> I also assumed that it's OK to send a commit message to djgpp-workers,

Yup, especially if there's something to add beyond what you put in cvs.

> since this is some new feature, on the basis that not everyone is on the
> djgpp-cvs list. Should I do this in the future too?

You can if you want, especially if we're discussing it anyway.  It's
not required.