delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp-workers/2001/01/06/18:11:09

From: "Tim Van Holder" <tim DOT van DOT holder AT pandora DOT be>
To: <djgpp-workers AT delorie DOT com>
Subject: RE: DJGPP CVS users
Date: Sun, 7 Jan 2001 00:11:50 +0100
Message-ID: <NEBBIOJNGMKPNOBKHCGHOEGCCAAA.tim.van.holder@pandora.be>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-reply-to: <200101062237.RAA24291@envy.delorie.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id SAA15586
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

> We've never done that, and starting now would be tricky.  We use cvs
> logs and the knowledge base for that.
I don't see how tricky it can be - all it takes is a single run of
rcs2log to create the initial version, and then some minor initial
editing to clean it up. Once it's there, requiring people who commit
changes to also include an addition to the ChangeLog would keep it
up-to-date (and if necessary, rcs2log could be run again to create
a fresh one based on the CVS logs (which would probably be identical
if the developers use emacs)). It would also provide a convenient
reference point for when CVS access is unavailable.
I'm quite willing to create that initial ChangeLog and post it, if
anyone is interested.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019