From: Russ Allbery <rra@stanford.edu>
Subject: Re: *** empty log message *** is a no-no
Date: 17 Nov 1999 13:37:29 -0800 [thread overview]
Message-ID: <yl3du43ili.fsf@windlord.stanford.edu> (raw)
In-Reply-To: Denys Duchier's message of "17 Nov 1999 15:17:10 +0100"
Denys Duchier <Denys.Duchier@ps.uni-sb.de> writes:
> Jan Vroonhof <vroonhof@math.ethz.ch> writes:
>> What do typically do when using CVS to document changes? use free
>> format?
> `C-x v =' to diff with the committed version. Then I document the
> changes in fairly free format. Typically, I have also added comments in
> the file documenting the new stuff, or making clear the invariants that
> should not be violated, etc... I also include these comments in the log
> entry.
As someone who uses both ChangeLogs *and* CVS commit messages for at least
one project, I actually put different information in both. The ChangeLog
gets the typical per-function brief change message; the CVS commit log
gets a free-form chatty description of what I changed and why from more of
an overall perspective.
When using CVS, I don't find the traditional ChangeLog format all that
overly useful, and if I drop one, I'll usually drop the ChangeLog in favor
of the CVS commit history and just generate the ChangeLog automatically
from the commit history. I find the noting of what functions changed in a
file to be considerably less useful than cvs annotate.
But a lot of this is driven by what sort of software one is writing.
--
Russ Allbery (rra@stanford.edu) <URL:http://www.eyrie.org/~eagle/>
next prev parent reply other threads:[~1999-11-17 21:37 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
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 [this message]
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=yl3du43ili.fsf@windlord.stanford.edu \
--to=rra@stanford.edu \
/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).