Greg Woods wrote:
[...]
> It makes me wonder though if a magic pseudo-tag could even be
> implemented right in the case of bumped release numbers without jumping
> through a whole lot of hoops. I can't at the moment think of a way to
> inidicate to RCS that the top of the trunk should be always used without
> getting the "default branch" stuff involved and messing with that
> doesn't work well with CVS either since it's effectively reserved for
> internal use only.
[smc] Yeah I think implementing what I want would
be pretty hard... But, the changes might be at least localized
to the RCS code, excepting any changes needed to handle a
tag name that begins with a dot, (i.e. ".trunk" or something
as mentioned in the docs. But that's a separate, perhaps
easier problem.)
> I guess if you are bull-headed enough to want to bump your release
> numbers (or stuck with a repository that was copied from an old RCS
> repository where this was the "right" way of doing things) then you can
> always just manually pick the right number to use when creating the
> TRUNK tag and indeed if you are insisting on continuing down such a
> questionable track you can still move the TRUNK tag every time you bump
> the release number.....
[smc] I'm not bull headed enough to go through
the work of manually making and maintaining a
TRUNK non-branch tag. Of course I don't _need_
a branch-tag name for the trunk either, I've lived
without it for quite some time just fine. I am bull
headed enough to want it anyway though. :) and
perhaps even bull headed enough to look at the
code some...but I think it will be a rather compilcated
thing to implement, For right now, I think I've
learned enough and said enough on this topic though.
-- steve
