[Top][All Lists]

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

Re: Do we have an alternative to tag, to record status of cvs repo

From: Paul Sander
Subject: Re: Do we have an alternative to tag, to record status of cvs repo
Date: Tue, 22 Apr 2003 10:01:27 -0700

You can drop down to RCS directly and craft your own CVS metadata to
get a speed-up.  As long as you can identify the proper revisions in
advance (i.e. by version number or branch/timestamp pair), read-only
operations on the RCS files are safe while bypassing the CVS and RCS
locking mechanisms.  (This assumes you're using Unix, of course.  Windows
might be a different story.)

--- Forwarded mail from address@hidden

In our orgn, we need to keep track of the code base status after each 
engineer's check in is done. We were using tagging to keep track of this. 
But the huge number of tags getting created over a long time have made the 
CVS repository bloated with tags. This is also making the sync. of 
repository with our branch located elsewhere too long.

I was wondering whether we have a whatfile kind of tool which was used in 
RCS(version no. of each file stored in a whatfile, which is used to check 
out the entire code base later). I tried to create a similar kind of tool 
using the CVS commands. I am able to create the info file by traversing 
through the Entries files in my local copy. But a check out using this file 
is taking around 4 hours, as I am issuing a check out command for each file 

Can any body give me a clue how to record the code base status, other than 
tagging, so that this can be used to check out the code later. I know that 
tag is the obvious solution. But I have problems with tagging, since it 
updates almost every file in the repo. This makes my update take too long.

--- End of forwarded message from address@hidden

reply via email to

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