From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/27032 Path: main.gmane.org!not-for-mail From: Russ Allbery Newsgroups: gmane.emacs.gnus.general Subject: Re: *** empty log message *** is a no-no Date: 17 Nov 1999 13:37:29 -0800 Sender: owner-ding@hpc.uh.edu Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no X-Trace: main.gmane.org 1035164130 22480 80.91.224.250 (21 Oct 2002 01:35:30 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 01:35:30 +0000 (UTC) Return-Path: Original-Received: from bart.math.uh.edu (bart.math.uh.edu [129.7.128.48]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id QAA20937 for ; Wed, 17 Nov 1999 16:39:28 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by bart.math.uh.edu (8.9.1/8.9.1) with ESMTP id PAB04683; Wed, 17 Nov 1999 15:38:18 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Wed, 17 Nov 1999 15:38:24 -0600 (CST) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id PAA09062 for ; Wed, 17 Nov 1999 15:38:15 -0600 (CST) Original-Received: from windlord.stanford.edu (windlord.Stanford.EDU [171.64.12.23]) by sclp3.sclp.com (8.8.5/8.8.5) with SMTP id QAA20919 for ; Wed, 17 Nov 1999 16:37:40 -0500 (EST) Original-Received: (qmail 22458 invoked by uid 50); 17 Nov 1999 21:37:29 -0000 Original-To: ding@gnus.org In-Reply-To: Denys Duchier's message of "17 Nov 1999 15:17:10 +0100" Original-Lines: 28 X-Mailer: Gnus v5.4.66/Emacs 19.34 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:27032 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:27032 Denys Duchier writes: > Jan Vroonhof 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)