Thanks Spiro I will take a look at cvs2cl.
Here is what happened. Branch B was created from Branch A. When branch B was created it was never built or tagged for a period of 12 days. In those 12 days files were committed to the Branch B and then the build happened. Along with the first build, came the first tag on all the files. Now I need to determine what files were changed during that 12 day period. If I can figure out somehow the date that Branch B was created, then I could create a tag based on the date. Also, without the tagging information, I'm not sure how I would create that missing tag on the branch. cvs rtag -D2008-01-01 NEW-START-TAG <module> would create the tag on HEAD, which I don't want. I want it to be created on Branch B. Norm. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Spiro Trikaliotis Sent: Saturday, June 21, 2008 5:00 AM To: [email protected] Subject: Re: Finding changes on a branch Hello Norman, * On Fri, Jun 20, 2008 at 12:39:58PM -0500 CRISP Norman wrote: > How can I find all the changes that occurred on a branch. I know of > the method using tags by start and end date but in this case the tags > on the branch were very poorly managed. Is it possible to use a date range? If I understand you correctly, the branch itself was not tagged correctly? In these cases, cvs2cl.pl (http://www.red-bean.com/cvs2cl/) does a fairly good job at finding out when the branch was created. Then, you can use this date info to create a tag for the branch point. Note that cvs2cl.pl might fail to find the exact date when there were consecutive checkins at the time the branch was created. Anyway, in most cases, you can find it out with not much hazzle. HTH. Beste Grüße, Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/
