[Top][All Lists]

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

Re: How to find the changes related to a check in?

From: Todd Denniston
Subject: Re: How to find the changes related to a check in?
Date: Tue, 01 Nov 2005 09:38:57 -0500

address@hidden wrote:
> Russ,
> I can use branch if necessary. I mainly do not like the merge step. At
> this time, the number of merge is the number of changes between two
> releases.
> I have used perforce before. Each checkin will has a change number.
> using that change number it is very easy to get the file names which
> were changed and what the changes are in those files. Is there a
> safe/easy way for CVS to do that?
> My current project need to a way to find the change related to SCR. The
> change is checked in branch based on the latest release tag. Thus using
> branch check in tag and last release tag, we can get the changes. But
> this way, the final trunk merge need too much work.

Three suggestions other than CVSNT, or posibly even in addition too.
1) implement rcsinfo + verifymsg [1] to make your coders put in appropriate
bug/change/SCR information with thier comments.

2) use a log consolidator like cvs2cl [2] to view the changes. As long as
developers do one commit for the whole change over the whole tree (good
practice), the change sets become quite visible in the output log.

3) Apply normal tags when ever you feel like it. I have a script that
applies a tag with known construction which just increments a number on the
end of the tag each time it is ran. If you had one which did a similar thing
so any of your users could call it after a checkin or perhaps a loginfo
{post commit} script might be a useable thing here, change sets would be
even more evident. 

BTW I also noticed you were branch tagging 2 files out of your entire tree
in your first message. from what I have read on this list in the past, if
you are going to branch, it is best practice to branch the entire project
(all the files in all the directories) at the same time for each branch.


  Note there is a included with CVSNT that does IIRC similar to
the red-bean perl version but seems to work under windows.
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]