On Jul 12, 1999, Petter Reinholdtsen <[EMAIL PROTECTED]> wrote:
> I was thinking about autogenerating the ChangeLog on every commit.
> Do you think this would be a good idea?
I usually prefer to write a ChangeLog entry while I hack the code, and
check that it's consistent with the patch at check-in time. The
attached script will show the list of changed files and extract the
ChangeLog entry (with cvs diff) for you to check, and then proceeds to
check the files in with the extracted ChangeLog entry as the commit
message. It doesn't handle multiple ChangeLog files, but this isn't
usually a problem if you're disciplined to check in sub-directories
before their parents, or to specify the list of files to check-in.
--
Alexandre Oliva http://www.dcc.unicamp.br/~oliva IC-Unicamp, Bra[sz]il
oliva@{dcc.unicamp.br,guarana.{org,com}} aoliva@{acm.org,computer.org}
oliva@{gnu.org,kaffe.org,{egcs,sourceware}.cygnus.com,samba.org}
** I may forward mail about projects to mailing lists; please use them
clcommit
