Kayed Alfi [mailto:[EMAIL PROTECTED] wrote: > It is preventing us from retrieving an earlier version > of the file to make changes to that particular source > code. OK, now we're getting a little closer to an answer. The next question is, why do you want to make changes to an earlier revision? Are you abandoning all the changes made since that earlier revision, or do you need to fix a bug in a released version?
If you want to abandon all the changes, then you can use the -p option and direct the output to the same file. For this example, suppose you want to revert to version 1.1: cvs update -p -r1.1 somefile > somefile [modify somefile] cvs commit somefile As I said, though, this will wipe out any changes that have been made since revision 1.1, so treat this option with care. Make sure that is really what you want to do. If you want to make a bug fix, then you need to make a branch, and make the corrections on that branch: cvs tag -b -rRelease1_1 Release1_1_branch cvs update -rRelease1_1_branch [modify somefile] cvs commit somefile See Branching and Merging in the CVS documentation for more information: http://www.cvshome.org/docs/manual/cvs-1.11.7/cvs_5.html#SEC54 If neither of these covers what you're trying to do, then please tell us more about why you need to modify an older version of a file. > The question that probably begs it self, could > I undue changes recursivly to a earlier versions of > file x. You could, but that would be a tedious way to do it. -- Jim Hyslop Senior Software Designer Leitch Technology International Inc. (http://www.leitch.com) Columnist, C/C++ Users Journal (http://www.cuj.com/experts) _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
