[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Changelog commit procedure/protocol.

From: Todd Denniston
Subject: Re: Changelog commit procedure/protocol.
Date: Mon, 22 Jan 2007 16:16:33 -0600
User-agent: Thunderbird (X11/20060909)

Paul van Delst wrote:

We've just started maintaining a changelog for some of our code. The way we use it is to write the changelog entries and then use those entries as the commit message when the code is checked in.

My (probably silly) question is: What is the recommended practice for committing the changelog? During the commit with the current set of files, or after the commit?

In my environment:
we use the changelog entries "as the commit message when the code is checked in", the same as you.

Then we use cvs2cl[1] anytime someone wants to see a change log.

When we want a formal changelog (AKA SVD) we take the output of cvs2cl and summarize it.

Summary, let CVS keep your change log and let it keep that log firmly attached to the files that were changed for it. :)

But as will all practices YMMV and it may not be the best or recommended 

If you happen to be running a version of CVSNT, there is a which at least at one time took the same options and gave similar results to the perl cvs2cl.

Todd Denniston
Crane Division, Naval Surface Warfare Center (NSWC Crane)
Harnessing the Power of Technology for the Warfighter

reply via email to

[Prev in Thread] Current Thread [Next in Thread]