Mail Archives: djgpp-workers/2001/01/07/04:00:43
> It's tricky, believe me. As an evidence, please look at standards.texi,
> the GNU coding standards document: it has a whole section on how to write
> good ChangeLog entries (and that section just got larger in the last
> version as I asked Richard Stallman to add some more there, because some
> of his requirements were never documented before).
>
> It is even trickier for people who don't use Emacs, and a very recent
> version of it, because then they need to watch out for all kinds of
> small gotchas and fix them by hand.
>
> So if we ask for ChangeLog entries, we will need to have a ChangeLog
> Police to enforce the standards. That's more workload on those who
> participate in peer reviews. Those people are already overworked, so
> please let's not add anything that isn't absolutely necessary.
I wasn't suggesting a GNU-standard ChangeLog; just some file (call it
CVSLogs.txt if you want) that would keep a central record of all CVS
log messages (useful when working off-line, for example).
> (And, btw, rcs2log doesn't DTRT in many cases, if you want the standard
> ChangeLog entries.)
It has is flaws indeed. I tried that cvs2cl.pl script Bill Currie suggested
and it seems to give much better results. As a drawback, it requires Perl.
- Raw text -