On Jan 5, 2006, at 16:46, Richard_Goodwin@hmco.com wrote:
> I would like to know how I can move a tag from one revision of a
> file (or
> set of files) to another. Esentially I am looking for something
> that has
> the ease of use that CVS tags do.
As you've discovered, tags in Subversion are different from tags in
CVS. Whereas in CVS, a tag is a property of a file (as I understand
it), in Subversion, a tag is nothing more than a directory.
> I am working to convert a project from CVS to subversion. In the
> current
> process fixes that are to be included in the release are marked via
> a tag
> (such as PENDING). The release builds then use this tag to get
> versions of
> files to be in the build. So, to add a fix to a build the developer
> tags
> the correct versions of the files with the PENDING tag. Usually,
> this means
> the tag is being moved from a previous version of a file to a new
> one. How
> can this functionality be duplicated in Subversion?
>
> I realize I could use a merge to a branch instead. But, does not
> have the
> ease of just moving a tag. In this case it just adds time to the
> process
> without adding more functionality. As the developer would have to
> merge
> into a second client workspace and then commit.
The Subversion paradigm would be to have a "pending" branch, then, as
you surmised. I have never used CVS, so I can't say whether
Subversion's way is more difficult...
There is no need to have a second working copy, if that's
inconvenient for you for whatever reason. You can "svn switch" your
existing working copy (or a subset of it) to the "pending" branch, do
the merge, then "svn switch" it back to trunk.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jan 5 23:23:47 2006