On 8/29/05, Huaer XC <[EMAIL PROTECTED]> wrote: > On 8/29/05, Russ Sherk <[EMAIL PROTECTED]> wrote: > >>I have a file, like f1.c, which has a revision history from > >>1.1.1.1->1.1->1.2->1.3. the current tip is 1.3, this file(f1.c) >>in > my working directory has minor modifications. Now I do: > >> cvs update -j1.1 f1.c > >Why? > I just want to check how "cvs up -j1.1 f1.c" works? It's not related > with my real research work. > > > > and then "pg f1.c", I found the file did not change >>anything. (there > > > is no sticky tags on f1.c). I am wondering how "cvs update >>-j1.1" > > > workaround??? > > Not sure what you mean. > Sorry for the confusion. should be: > the operation "cvs up -j1.1 f1.c" did nothing on the file f1.c under > my working directory.. I dont know why? while the following command > worked fine: > > cvs -q up -p -r1.1 f1.c > f1.c This replaces local f1.c with cvs revision 1.1 of f1.c. > > and this does not change the revision history of f1.c.. Until you commit. When you commit, the history will be updated on the branch you commit to (the branch from which the orrigional f1.c was checked out from or last switched to). Another note is that it will be committed to the tip of the main trunk/branch. Otherwise you will not be able to commit (cvs will give you the 'version 1.1 is not a branch. correct the above errors before committing.' error.... this is the only reason the history will not be changed: if you don't commit then the change is to the sandbox only, not the repository.)
--Russ > > > > BTW. I am using cvs: version 1.12.12.. > thanks > _______________________________________________ Info-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/info-cvs
