RE: local tagging

[Volpe, Christopher R (Research)]

No, that doesn't work. I don't want the state of the *repository* on a given 
date. I want the state
of the files in my *working* directory at a given moment. Some of those file 
will often not be the
most recent version, expecially, as often happens, if I know that someone has 
checked in changes to
some files that I know are going to temporarily mess me up while I'm working on 
something else. It
seems to me that this is precisely the reason why "cvs tag" (as opposed to "cvs 
rtag") exists, but
again, I don't want to actually touch the repository files in the process.

> -----Original Message-----
> From: Donald Sharp [mailto:address@hidden
> Sent: Tuesday, December 10, 2002 11:33 AM
> To: Volpe, Christopher R (Research)
> Cc: 'address@hidden'
> Subject: Re: local tagging
> 
> 
> Just grab the Date of the latest change you want and then 
> when you want to go back do a cvs update -D <date> -r <branch>
> 
> donald
> On Tue, Dec 10, 2002 at 11:12:26AM -0500, Volpe, Christopher 
> R (Research) wrote:
> > Hi folks-
> >   I'm new to the list, so I apologize if this has been 
> asked. I perused the last few months of
> > archived messages, but couldn't find the FAQ referred to on
> > http://mail.gnu.org/mailman/listinfo/info-cvs. 
> >   
> >   Anyway, here's what I'd like to be able to do. I want to 
> have the equivalent functionality of a
> > tag, but without actually writing to the repository. That 
> is, I want to record the state of the
> > revisions of all the files in my working directory so that 
> I can revert to that state at a later
> > time. But I don't want to modify the repository itself, for 
> a couple of reasons:
> > 
> > 1) The repository is shared by a large community, and the 
> owners don't like the prospect of having a
> > user (much less *many* users) creating more than one or two 
> tags a year.
> > 2) The functionality needs to be available from a shared 
> testing account that has read-only anonymous
> > access to the repository.
> > 
> > Now, the straightforward solution would be to write a 
> script, or a pair of scripts, that does a "cvs
> > status", and parses the output and writes it out in a 
> condensed form, and another that reads this
> > condensed form and pulls out all the specified file 
> revisions. However, before I go reinventing the
> > wheel, I'd like to know if there exists such a tool 
> already, possibly with more bells and whistles
> > than I was planning to implement. Thanks in advance for any 
> information you can provide.
> > 
> > 
> > Chris
> > > GE Global Research Center 
> > > 
> ______________________________________________________________
> _____________________________________
> > > _______________________________________________
> > > 
> > Dr. Christopher R. Volpe, Ph.D.
> > Computer Scientist
> > Visualization and Computer Vision Lab 
> > Imaging Technologies
> > Bldg KW, Room C215
> > P.O. Box 8, Schenectady, NY 12301
> > 
> > (518) 387-7766, Dial Comm: 8*833-7766, Fax: (518) 387-6981
> > e-mail: address@hidden    web: 
http://www.crd.ge.com/~volpecr
> 
> 
> 
> 
> 
> _______________________________________________
> Info-cvs mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/info-cvs