[cvsnt] How to go backwards in revisions -- easiest way?

[Jeff Urlwin]

Erik,

Thanks,

In this case, there were about 50 or 60 files modified (but not all in the
same directory) and not all the same revision.  Each one would have had to
be done manually, since the best revision was two revs ago, not necessarily
the same on each.  It would have been a pain to do each one individually.
Sounds like a perl script would have done it, but this was faster...

Thanks,

Jeff

> -----Original Message-----
> From: cvsnt-bounces at cvsnt.org 
> [mailto:cvsnt-bounces at cvsnt.org] On Behalf Of Erik Anderson
> Sent: Wednesday, November 05, 2003 1:10 PM
> To: cvsnt at cvsnt.org
> Subject: Re: [cvsnt] How to go backwards in revisions -- easiest way?
> 
> 
> The method to backtrack is the same method used to merge in 
> changes from a different location.  If you are using the 
> command line, pass two -j parameters, the first being the 
> revision *after* the changes, and the second being the 
> revision *before* the changes.
> 
> In the end, though, you will get the same effect as the 
> method you used, although this is less likely to upset other 
> changes done since then.
> 
> ----- Original Message ----- 
> From: "Jeff Urlwin" <jurlwin at esoftmatic.com>
> To: <cvsnt at cvsnt.org>
> Sent: Wednesday, November 05, 2003 9:47 AM
> Subject: [cvsnt] How to go backwards in revisions -- easiest way?
> 
> 
> Hi,
> 
> This feels like a stupid question, since it seems it should 
> be obvious and I'll probably say "Doh" when I get the answer, but...
> 
> I simply wanted to move back a revision and start again, 
> after making a mistake.  I knew the revision as of yesterday 
> was good, so I ended up checking out with a sticky tag on the 
> date.  From there, though, I couldn't check back in because 
> of the sticky tag.  I received an error message from the server.
> 
> What I ended up doing was copying all the files to another 
> directory, checking out without the sticky tag (sticky tag 
> reset), copying the files back in and forcing a check in.  
> That seems like a hard way to do the work. I suppose I could 
> have administratively deleted revisions, but that would have 
> taken a fair amount of time, going through the files changed 
> one by one.
> 
> So, my question is: is there an easier way to 'revert' to an 
> earlier version to avoid a problem?
> 
> Note (if it makes a difference), we have 3 developers and are 
> all working off the main trunk.  We typically don't setup a 
> development branch unless we are supporting an older version, 
> while new work is in progress.
> 
> Thanks,
> 
> Jeff
> 
> 
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
> 
> _______________________________________________
> cvsnt mailing list
> cvsnt at cvsnt.org http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt
>