Nick Seigal wrote:
> My solution to Alex's problem is that a tag of my project containing
> externals should only be containing externals pointing at other tagged and
> unchanging repository codelines. These should never be changed or deleted
> (hance the idea of a "tag"), and I can insure this, since we maintain our
> own vendor-library and internal-library branches and their policies (see
> above). In fact, the discussion of a "read-only tag" seems strange, since
> this seems to be the only thing that really seperates a tag from a branch.
Thanks Nick, I've too arrived to this conclusion. My case is a bit more
annoying because I'm modifying the external library too from the main
project, so I can't link to a "frozen" revision of the library ATM. Thus
when I make a milestone for the project, I must go to make tags for all
the external libraries involved and make new external ad-hoc properties
for the milestone tag.
Seeing that this issue is likely to be beating on developers for time to
come, I wonder if there's some plan to address it in the svn roadmap.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jan 17 12:40:43 2005