"Larry Jones" <[email protected]> wrote in message
> Gary writes:
> > One thing I've noticed which is causing a problem is that there appears
> > be a problem with rtag -b commands in that the revision number for the
> > is incorrect, e.g. the branch tag should be revision 184.108.40.206 but comes
> > as 2.4.2 with no other indication that it was a branch tag.
> 220.127.116.11 is a "magic" branch tag -- the actual branch *is* 2.4.2. You
> know it's a branch because there's an odd number of components.
Sorry, I completley misled you there. I'd be happy if the taginfo hook
received an odd number of components but it doesn't.
If I add a branch tag to revision 18.104.22.168, the information that comes
through from taginfo is simply 22.214.171.124 with no indication that there was a
branch tag, niether the magic revision or the three component version -
either would be good but as far as I can see, you can't tell from the
informaiton provided by taginfo wether the tag operation was a tag or a
info-cvs mailing list