Date:	Sat, 6 Jan 2001 15:53:36 -0700
From:	Bill Currie <bill AT taniwha DOT org>
To:	djgpp-workers AT delorie DOT com
Subject:	Re: DJGPP CVS users
Message-ID:	<20010106155336.E17172@taniwha.org>
Mail-Followup-To:	djgpp-workers AT delorie DOT com
References:	<NEBBIOJNGMKPNOBKHCGHIEGBCAAA DOT tim DOT van DOT holder AT pandora DOT be> <200101062237 DOT RAA24291 AT envy DOT delorie DOT com>
Mime-Version:	1.0
X-Mailer:	Mutt 1.0.1i
In-Reply-To:	<200101062237.RAA24291@envy.delorie.com>; from dj@delorie.com on Sat, Jan 06, 2001 at 05:37:01PM -0500
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

On Sat, Jan 06, 2001 at 05:37:01PM -0500, DJ Delorie wrote:
> > Alternatively, how about including a ChangeLog in the top dir of the
> > DJGPP CVS tree?
> 
> We've never done that, and starting now would be tricky.  We use cvs
> logs and the knowledge base for that.

You can also use the cvs2cl.pl script. That's what we use in quakeforge: part
of our release process is "make changelog" (and when sourceforge's loginfo
support broke for a few weeks, what we relied on to see what was happening).
IMHO, no file that can be generated (easily) should be in cvs, and ChangeLog
is one of them :)

If you can't find cvs2cl.pl on the web (should be able to, I did find the home
page once), it's in tools/cvs2cl in the quakeforge tree
http://cvs.sourceforge.net/cgi-bin/cvsweb.cgi/newtree/tools/cvs2cl/?cvsroot=quake

Bill
-- 
Leave others their otherness. -- Aratak

- Raw text -