On Fri, 2006-11-17 at 22:17, Tim Hill wrote:
> Understood. But in this case I would argue that the tagging feature
> set is incomplete, because if you follow this logic, it would argue
> for a system that used tags as the primary tracking tool instead of
> rev#. However, there are still rather too many places in the
> "approved" svn workflows where logs are examined to extract revnums,
> which are then used in subsequent commands. (See, for example, the
> discussions on branching in the svn book).
What workflow 'follows' a tag? If you commit your workspace to
the trunk or wherever you are working _and_ copy it to the
tag from your workspace, you know what is in the tag and you've
made the change available for the ongoing work. If other
changes are happening on the trunk, other ways of making the
tag may not end up with the same thing you have. What if
someone else commits changes before yours and you don't
update before your commit? This means your workspace may
always be in the 'mixed-rev' mode and you won't want the tag
to match any other repository state.
--
Les Mikesell
lesmikesell@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Nov 18 05:58:31 2006