Just my 2 cents:
If anybody does go through with implementing this stuff, branch "functions"
(I believe somebody else already mentioned this in passing) seem to make more
sense to me than more magic tags.
Rather than a bunch of new magic tags, excepting perhaps '.trunk', allow
magic functions such as, '.parent', '.tail', and '.head' to be appended to
branch tags. Allow multiple concatenations, of course, for constructs like,
'current_branch.parent.parent.tail' and 'current_branch.parent.head' and
'.trunk.head'. Also, assume an empty tag is the current branch ( '.parent'
would be equivalent to 'current_branch.parent').
It seems to me that this would be almost as simple to implement as that list
of magic tags if you were inclined to do such - I think the lookup simply
becomes recursive somewhere, and adds the most extensible functionality.
Derek R. Price
CVS Solutions Architect
303.554.8291
[EMAIL PROTECTED]
http://alumni.engin.umich.edu/~oberon/resume.html
--
Photons have mass? Who would have guessed they were Catholic?!
"Cameron, Steve" wrote:
> 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
