Subject: Re: Please stop change logs in CVS commit messages
To: NetBSD Packages Technical Discussion List <tech-pkg@NetBSD.ORG>
From: Greg A. Woods <firstname.lastname@example.org>
Date: 07/11/2001 11:15:04
[ On Wednesday, July 11, 2001 at 09:47:13 (+0200), Tomasz Luchowski wrote: ]
> Subject: Re: Please stop change logs in CVS commit messages
> I always put contents of pkg/DESCR when I import new package, this time is was just very short.
> I'd still vote for long description of *new* packages so we can read what features it has
> and decide whether we want to try out the new package or not.
There is really no need for a long description under any circumstances.
By the time you can try the package out you've got the DESCR file
locally and you can read it directly at your convenience. Including it
in any commit message is waseful on many many fronts!
The purpose of putting the one-line COMMENT into the commit of
doc/pkg-CHANGES is to serve as a hint that reading the DESCR file (as
well as other possible future investigation) is desirable. To this end
I keep those doc messages temporarily in a folder just for this purpose
(i.e. until I get the chance to go look, and of course until the change
actually shows up in the anonymous CVS repo!).
There have been a few times where the short description sounded so
interesting I wasn't willing to even wait for anon-CVS so I just did a
google search. In those cases the HOMEPAGE line would have helped, but
obviously wasn't really necessary.
Greg A. Woods
+1 416 218-0098 VE3TCP <email@example.com> <firstname.lastname@example.org>
Planix, Inc. <email@example.com>; Secrets of the Weird <firstname.lastname@example.org>