OK, that's what I figured... "floating label" sounds like about what I
was looking for.
Do people not generally use tags for maintenance to already-released
versions? Or is that ordinarily done with branches? (I'm still a
little unclear on the best practices and conventions surrounding those
For my stuff, I'll stick with the rm/cp method, or really just not
tagging a version until I'm sure I'm done with it :-)
On 9/29/06, Reedick, Andrew <Andrew.Reedick@bellsouth.com> wrote:
> > -----Original Message-----
> > From: Dan Crosta [mailto:firstname.lastname@example.org]
> > Sent: Friday, September 29, 2006 3:45 PM
> > To: email@example.com
> > Subject: updating a tag
> > is there a simple idiom to use for updating a tag which already exists
> > to reflect the current contents of a working copy or of the /trunk
> > part of the repository? if you just reissue the svn cp command, it
> > will create a subdirectory of the tag directory (i found out the hard
> > way), and deleting and re-copying the tag causes 2 revisions rather
> > than 1. is there some idiom for ... basically updating a tag or branch
> > to the current contents of the trunk?
> In theory, tags shouldn't be modified once created.
> If you need to update a tag, you can either treat like a branch and just
> update it normally. 'svn co svn://.../some_tag, svn commit'
> Or you can recreate the tag, by deleting the tag and then creating a new
> tag with the same name. This is probably the better approach for your
> case. (Sounds like you want a 'floating label.')
> If you need to reference the previous tags, then you can rename or move
> the tag instead of deleting it. Otherwise you'll need to read up on peg
> branches to access previously deleted tags.
> If you don't want to delete/rm/mv the tag, then you'll need to merge the
> trunk to the tag. You'll need a script to automatically accept the
> trunk's version in case of merge conflicts (not that there should be
> any) by copying foo.java.right-r123 to foo.java.
> The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential, proprietary, and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from all computers. GA622
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Sep 29 22:02:57 2006