From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6870 invoked from network); 24 Oct 2001 00:05:49 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 24 Oct 2001 00:05:49 -0000 Received: (qmail 8403 invoked by alias); 24 Oct 2001 00:05:41 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 16129 Received: (qmail 8343 invoked from network); 24 Oct 2001 00:05:37 -0000 From: Bart Schaefer Message-Id: <011023170532.ZM19347@candle.brasslantern.com> Date: Tue, 23 Oct 2001 17:05:32 -0700 In-Reply-To: Comments: In reply to Wayne Davison "Re: ChangeLog formatting?" (Oct 23, 4:37pm) References: X-Mailer: Z-Mail Lite (5.0.0 30July97) To: zsh-workers@sunsite.dk Subject: Re: ChangeLog formatting? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Oct 23, 4:37pm, Wayne Davison wrote: > > On Tue, 23 Oct 2001, Adam Spiers wrote: > > Would be nice to have a convention for cvs commit log messages too. > > In what way were you thinking? I'd be cautious of too much > conformance, but some basic guidelines could be useful. For zsh, I generally try to keep my commit log messages less than one line long so I can easily pass them in the -m option of "cvs commit". If you want the full story, read the ChangeLog. Normally I'd just let CVS bring up the editor for each directory and type a description of each file as they're shown to me, but I'm committing to the cvs.zsh.sf.net server over a slow enough link that I get timeouts if I don't keep the messages very brief and let the whole process run in one swoop.