Re: Tags on a branch

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jim Hyslop <address@hidden> writes:

> Norman Crisp wrote:
> > Hello all,
> > 
> > Is there a way to produce a list of all tags that has been used in a
> > branch?
> 
> I think the only way to tell would be to write a script, and compare the
> numeric revision of the symbolic tags against the numeric revision of
> the branch tag.
> 
> For example, if 'cvs status -v' shows:
> Existing tags:
>       tag_a           (revision: 1.3.2.3)
>       the_branch      (branch: 1.3.2)
>       tag_b           (revision: 1.4)
> 
> then tag_a is on the branch tag_b is on the trunk.
> 
> This might have to be done on a file-by-file basis.

I believe it would need to be on a file-by-file basis... AND there is no
general method to tell if tag_1, tag_2, tag_3, tag_4, tag_5 which are
all the same revision are logically on the parent branch or on the
various other branches that exist... unless there has been commits to
the branch and those commits correlate in a reasonable manner across all
of the instances of the tagname in all files.

   tag_6         (revision: 1.2)
   tagd_branch   (revision: 1.2.8)
   tag_5         (revision: 1.2)
   tag_4         (revision: 1.2)
   tagc_branch   (branch: 1.2.6)
   tag_3         (revision: 1.2)
   import_vend2  (revision: 1.1.1.2)
   tagb_branch   (branch: 1.2.4)
   tag_2         (revision: 1.2)
   taga_branch   (branch: 1.2.2)
   tag_1         (revision: 1.2)
   import_vend1  (revision: 1.1.1.1)
   vendor        (branch: 1.1.1)

In one directory of files, a 'foo' tag might be a revision tag while
in a different set of files the same tag might be a branch tag name.

I believe that the libcvs project has some tooling to try to help you in
this regard, but do recall that folks can come back after the fact and
move revision tags to new releases or rename existing tags or even
delete revisions from ,v files.

        Good luck,
        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)

iD8DBQFEQJWNCg7APGsDnFERApBgAJ4tb5hnIwktRpLVYyIlZD+k2dXDawCfRhc7
JOOqaQxnVyeEGppObE/KAo8=
=GZ8j
-----END PGP SIGNATURE-----