View Single Post
  #3   (View Single Post)  
Old 1st April 2018
vns3 vns3 is offline
Port Guard
 
Join Date: Sep 2017
Posts: 25
Default

Thank you for responding, your answer inspired me to do a little more poking around and now I think I understand.

I can just update the ports tree using the branch tag I am moving to.

In case others stumble on this post, this link explains it a little more clearly, under the "Accessing Branches" header:

http://cvsgui.sourceforge.net/howto/cvsdoc/cvs_5.html

Quote:
Accessing branches

You can retrieve a branch in one of two ways: by checking it out fresh from the repository, or by switching an existing working copy over to the branch.

To check out a branch from the repository, invoke `checkout' with the `-r' flag, followed by the tag name of the branch (see section Creating a branch):

$ cvs checkout -r rel-1-0-patches tc

Or, if you already have a working copy, you can switch it to a given branch with `update -r':

$ cvs update -r rel-1-0-patches tc

or equivalently:

$ cd tc
$ cvs update -r rel-1-0-patches

It does not matter if the working copy was originally on the main trunk or on some other branch -- the above command will switch it to the named branch. And similarly to a regular `update' command, `update -r' merges any changes you have made, notifying you of conflicts where they occur.

Once you have a working copy tied to a particular branch, it remains there until you tell it otherwise. This means that changes checked in from the working copy will add new revisions on that branch, while leaving the main trunk and other branches unaffected.

To find out what branch a working copy is on, you can use the `status' command. In its output, look for the field named `Sticky tag' (see section Sticky tags) -- that's CVS's way of telling you the branch, if any, of the current working files:
Reply With Quote