Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: *** empty log message *** is a no-no
Date: 12 Nov 1999 13:13:49 +0100	[thread overview]
Message-ID: <m3aeoj9abm.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <is1z9v537x.fsf@talo.ps.uni-sb.de>

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


  reply	other threads:[~1999-11-12 12:13 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-12 10:57 Steinar Bang
1999-11-12 12:00 ` Denys Duchier
1999-11-12 12:13   ` Lars Magne Ingebrigtsen [this message]
1999-11-12 12:19     ` Steinar Bang
1999-11-12 12:33       ` William M. Perry
1999-11-12 12:51         ` Steinar Bang
1999-11-12 12:25     ` Kai Großjohann
1999-11-12 13:33       ` David Kågedal
1999-11-12 14:28     ` Alexandre Oliva
1999-11-12 18:23       ` Lars Magne Ingebrigtsen
1999-11-12 20:04         ` Per Abrahamsen
1999-11-15  7:39           ` Steinar Bang
1999-11-15  8:39             ` Per Abrahamsen
1999-11-15 10:02               ` Steinar Bang
1999-11-15 16:32                 ` Per Abrahamsen
1999-11-16  8:51                   ` Steinar Bang
1999-11-16 16:05                     ` Per Abrahamsen
1999-11-17  8:02                       ` Steinar Bang
1999-11-17 12:42                         ` Denys Duchier
1999-11-17 14:38                           ` Kai Großjohann
1999-11-17 13:35           ` Jan Vroonhof
1999-11-17 14:39           ` Jan Vroonhof
     [not found]           ` <whg0y8430s.fsf@viffe <byemdpi3na.fsf@urysohn.math.ethz.ch>
1999-11-17 16:06             ` Denys Duchier
     [not found]           ` <whg0y8430s.fsf@viffe <byogctgs0h.fsf@urysohn.math.ethz.ch>
1999-11-17 14:17             ` Denys Duchier
1999-11-17 21:37               ` Russ Allbery
1999-11-17 19:20             ` Lee Cantey
1999-11-17 20:47           ` Jan Vroonhof
1999-11-18 12:55           ` Jan Vroonhof
     [not found]           ` <whg0y8430s.fsf@viffe <byr9hoq7qk.fsf@bolzano.math.ethz.ch>
1999-11-18 22:36             ` Russ Allbery
1999-11-16  2:20         ` Alexandre Oliva
1999-11-16 16:56           ` Lars Magne Ingebrigtsen
1999-11-16 18:13             ` Lee Cantey
1999-11-16 19:24               ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m3aeoj9abm.fsf@quimbies.gnus.org \
    --to=larsi@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).