From: Jorgen S. <fo...@fo...> - 2005-01-20 01:28:02
|
Hi there. I noticed that recently, people are keeping a ChangeLog in CVS. Why? We used to use cvs2cl to generate the ChangeLog from the CVS messages. Keeping a separate ChangeLog file seems to duplicate data for no obvious gain at all. Since it's the worst possible case that some people don't add entries to the ChangeLog, and some do, I think we should settle on a policy for this. 1) I'm strongly against keeping duplicate information. I.e. either ChangeLog or CVS commit messages die. 2) I'm strongly in favor of keeping revision information in the revision control system, and not in a file separate from the revision control system. I.e. keep the CVS commit messages. 3) Of course, a ChangeLog is important for releases. I.e. use cvs2cl for a release. Greetings, -- Jorgen -- ((email . "fo...@fo...") (www . "http://www.forcix.cx/") (gpg . "1024D/028AF63C") (irc . "nick forcer on IRCnet")) |