If both revisions are tagged you don't have to do this a file at a time.
You could try merging by date as well.
http://www.cvshome.org/docs/manual/cvs_5.html#SEC62
And make sure you don't have any work which hasn't been checked in and which
hasn't been backed up in there before you start guessing.
Derek
--
Derek Price CVS Solutions Architect ( http://CVSHome.org )
mailto:[EMAIL PROTECTED] OpenAvenue ( http://OpenAvenue.com )
--
My name is not Dr. Death.
My name is not Dr. Death.
My name is not Dr. Death...
- Bart Simpson on chalkboard, _The Simpsons_
Aldo Longhi wrote:
> >On Sat, 23 Sep 2000, Bill Shields wrote:
> >>
> >>Question: What is the best way to revert all the files back to the
> >>previous individual versions that were good?
> >
> >$ cvs update -j <cur_vers> -j <prev_vers> <file>
> >$ cvs commit <file>
> >
> >This only works if the latest version is the one you want to get rid
> >of. If there have been changes made since the bad versions were
> >commited, then you'll have a litte more work to do...
> >
> >You'll have to do this for each file, or write a script to do it
> >for you.
> >
> >Garth
>
> What about this instead:
> ("foo" is the file in question)...
>
> $ cvs up -r <good_vers> -p foo > foo
> $ cvs ci foo
>
> This will get the version that you want, overwrite
> your existing local copy, then check it in as the
> latest version.
>
> - Aldo
>
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
> Share information about yourself, create your own public profile at
> http://profiles.msn.com.
>
> _______________________________________________
> Info-cvs mailing list
> [EMAIL PROTECTED]
> http://mail.gnu.org/mailman/listinfo/info-cvs
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
