Reinhard Brandstaedter wrote:
> a complex tag is a tag created from a working copy that contains not one
> single revision of a whole directory tree but where single
> folders/subtrees or files are selectively checked out from different
> revisions or even locations/branches.
>
> I'm talking about using complex tags for tagging stable versions or
> releases of production projects. Why? Because developers and project
> leads at my company do it that way and I think it's bad and have to
> convince them it's bad
>
> In my opinion using a complex tag to tag a version/release of an project
> is really bad because:
>
> a.) it's difficult to track which folders in the tag came from which
> original revision or location. If you want to know where they came from
> you have to check each folder in the log for it's "copy-from"
>
> b.) resulting from a.) it's almost impossible to recreate such a tag
> unless you still have the exact working copy you used before. Assuming
> the complex tag is gone (I mean GONE, not in repository history or
> whatever - unrecoverable) and the working copy is gone (who keeps
> working copies stable forever?) you can't recreate the version just with
> the history on trunk.
How do you make a tag GONE? Surely the whole point of a revision control
system is that nothing is ever gone?
--
Nikki Locke, Trumphurst Ltd. PC & Unix consultancy & programming
http://www.trumphurst.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 15 15:30:33 2006