Gnus development mailing list
 help / color / mirror / Atom feed
From: Jan Vroonhof <vroonhof@math.ethz.ch>
Subject: Re: *** empty log message *** is a no-no
Date: 17 Nov 1999 14:35:42 +0100	[thread overview]
Message-ID: <byogctgs0h.fsf@urysohn.math.ethz.ch> (raw)
In-Reply-To: Denys Duchier's message of "Wed, 17 Nov 1999 12:45:15 GMT"

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

> `C-x v a' will create a ChangeLog file for you from the cvs log
> entries.  There is no reason to _maintain_ a ChangeLog file,
> especially since it contains less precise information than the cvs log
> (e.g. time stamps).

The advantage of Changelogs is that you can write them at the time the
change is made, not at the time of commit. In addition Changelogs
contain the function/variable affected by the change and there is
support from Emacs to add them automatically.
Is there a way to have the same for CVS logs? What do typically do
when using CVS to document changes? use free format?

Is the resolution on the time stamps that important?

Jan



  parent reply	other threads:[~1999-11-17 13:35 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
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 [this message]
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=byogctgs0h.fsf@urysohn.math.ethz.ch \
    --to=vroonhof@math.ethz.ch \
    /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).