Re: *** empty log message *** is a no-no

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

Denys Duchier <Denys.Duchier@ps.uni-sb.de> writes:

> I absolutely concur.  I was about to suggest the very same thing.
> Personally, when I implement something new, I usually include full
> documentation in the log message.  This way (1) others reading the
> logs are well informed about what I have done, (2) when I get around
> to writing actual documentation, I already have an outline of it in
> the logs.  When fixing a tricky bug, it is also a good idea to
> document your understanding of it.  My view is that the CVS logs serve
> the dual purpose of keeping everyone informed about on-going progress
> in the project as well as of being a persistent repository of useful
> information/documentation.

The ChangeLogs are the log files for Gnus.  So if we could get the
ChangeLog generated from the CVS logs (or the other way around,
preferably), that would be neat.

(And I always write documentation while implementing new stuff.
(Well, almost always. :-)  It's an integrated part of programming for
me.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   larsi@gnus.org * Lars Magne Ingebrigtsen