7.4. Sticky tags

The `-r release-1-0-patches' flag that was given to checkout is sticky, that is, it will apply to subsequent commands in this directory. If you commit any modifications, they are committed on the branch. You can later merge the modifications into the main trunk. See Merging.

$ vi driver.c   # Fix the bugs
$ cvs commit -m "Fixed initialization bug" driver.c

Checking in driver.c;

/usr/local/cvsroot/yoyodyne/tc/driver.c,v  <--  driver.c

new revision: 1.7.2.1; previous revision: 1.7

done

$ cvs status -v driver.c

===================================================================

File: driver.c          Status: Up-to-date


    Version:            1.7.2.1 Sat Dec  5 19:35:03 1992

    RCS Version:        1.7.2.1 /usr/local/cvsroot/yoyodyne/tc/driver.c,v

    Sticky Tag:         release-1-0-patches (branch: 1.7.2)

    Sticky Date:        (none)

    Sticky Options:     (none)


    Existing Tags:

        release-1-0-patches             (branch: 1.7.2)

        release-1-0                     (revision: 1.7)

The sticky tags will remain on your working files until you delete them with `cvs update -A'. See update.

Sticky tags are not just for branches. If you check out a certain revision (such as 1.4) it will also become sticky. Subsequent `cvs update' will not retrieve the latest revision until you reset the tag with `cvs update -A'.

See the descriptions in Appendix A for more information about sticky tags. Dates and some other options can also be sticky. Again, see Appendix A for details.

Prev: Creating a branch Up: Branches Top: Top