[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

How to properly create a new branch from an existing tag?

From: Richard Cook <awhig_at_yahoo.com>
Date: Fri, 4 Jan 2008 11:45:31 -0800 (PST)


My co-worker created a tag. We then assumed that we could create a branch at some point in the future by creating a tag referencing the Revision number of the tag. If I look in the repo-browser, Revsion # is 1110 next to the tag name. So when I choose Branch/Tag in TortoiseSVN, I select "Specific Revision in repository", and type in 1110. FYI, if I click the "..." button, I do not see this revision # listed in the log. The revision #'s go from 1109 and then jumps to 1111.

When I then compare the newly created branch to the tag, there are differing files. This does not seem correct to me. Am I doing something wrong here?

One thing that may be relevant. My co-worker had some files that were modified in his working copy, and were not checked in. When he created the tag, he did so from his working copy. If you look at the actions for revision 1110, you can see that these files are listed as being modified (they are listed as revisions 1108 and 1109). These exact files are the ones that are differing when comparing the tag and the new branch. I think if he had checked these files in, and then did a tag, we would not be having this problem. Unfortunately, he can not check those files in for a few reasons (they are config files).

What is the proper way to create a branch from a tag? I can not find any documentation for this?

I have successfully created the branch that I want, that contains the exact files as the tag by using revision 1109. This is not satisfactory to me as I want a foolproof way to create a branch from the tag. Or is the proper way to do this is to always take the tag's revision # and subtract 1 from it? This seems hacky to me.

Thanks for any help,
Received on 2008-01-04 20:45:43 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.