Re: cvs updating sticky tags

[Jim Hyslop]

address@hidden wrote:
> Jim Hyslop wrote:
>
> > An important thing to note is that the -D flag always selects revisions
> > from the default branch (which is usually the trunk, unless you have
> > used 'cvs admin -b').
>
>
>
> Thanks for the tip Jim.

You're welcome.

> Though could you please elaborate how "cvs admin -b" works?
>
> I have noticed now that my updates pull from head, even though I ran
> cvs admin -b on my local checkout. It seems to run over the tree with
> 'RCS done' messages.
>
> How can I tell what is the default branch to avoid this happening?

'cvs log -h' will show the header info of the log. One of the fields it 
shows is "branch:"

If a default branch is set, then the numeric revision (not the symbolic 
tag, unfortunately) of the branch point will be shown, for example:

$ cvs lo -h test.txt

RCS file: /my_documents/local_cvs/cvs-test/test_default/test.txt,v
Working file: test.txt
head: 1.1
branch: 1.1.2
locks: strict
access list:
symbolic names:
        hi: 1.1
        abranch: 1.1.0.2
keyword substitution: kv
total revisions: 2
=============================================================================

On this file, the default branch is 1.1.2, which (if you look at the 
symbolic names) corresponds to the tag 'abranch'.

If the default branch is set, there will be no value in the "branch:" field.

The default branch can be cleared by just issuing 'cvs admin -b'.

--
Jim