Hi,

I am trying to understand how sticky tags 
work (or they are useful). One way is to 
identify branches, this seems pretty clear.
The other way is (according to the manual),
to allow a user to avoid updating a portion 
of a larger tree into his working copy.
I then tried to imagine a scenario when this
applies. Suppose I have files file_1 and
file_2 in the repository, and I want to
keep up with the modifications other users
perform on file_1, but not on file_2.
I want to incorporate the other users 
modifications on file_2 only when I've 
finished my own modifications.
Then the sequence of commands to achieve 
this is:

cvs co file_1 (-> to get the last revision 
                say 1.5)
cvs co -r1.3 file_2 (-> to get a specific 
                        revision I want to
                        work on)
# edit file_1 and file_2

cvs update file_1 file_2 (-> this will update 
                        only file_1, and keep 
                        file_2 unchanged)
cvs commit file_1 file_2

# edit file_1 and file_2
cvs update file_1 file_2
cvs commit file_1 file_2
...

And when I want to integrate others' modifications
on file_2, I do:

cvs update -A file_1 file_2
cvs commit file_1 file_2

Is this the way it works (are my suppositions
and scenario above right)?

Thanks,
Irina.

_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Reply via email to