Creating the ChangeLog

Victor Tavares asks: "It is always expected to find a file called 'ChangeLog' or something similar in most software source tarballs. There is a section in the GNU Coding Standards document about them, but I have seen many different formats for ChangeLogs. Is there a standard way of creating ChangeLogs when using CVS/Emacs/ (insert your favourite tool) to manage the development? Are there ChangeLog tools or converters?"

Yes, there is a script, cvs2cl.pl

[kfogel]

I've just finished it. :-) It runs cvs log and
parses the output, producing a ChangeLog
file. Yes, it unifies when different files
have the same log message on the same date.

You can get it from me by asking, or check
it out via anonymous CVS:

cvs -d \
:pserver:[e-mail]:/usr/local/c vs

checkout cvs2cl

(password is "the key")

-Karl Fogel

What about vim?

[Delta]

Great, so now all those emacs ppl out there have a answer, but that's only answering half the question. And (personal opinion) it's a horrible answer.

What you all want him to do is use emacs for this. I don't like emacs, and I think that every user should be allowed to use the editor of his choice and still be part of the development.

Anyone care to address the other half here? Being CVS. CVS have all the logging one need for the ChangeLog file, surely there must be some script to convert it to ChangeLog and save it??

What about vim?

[claw-against-sun]

There is rcs2log script in contrib/ directory of cvs distribution.