Force revision update when creating a tag
Hi, A coworker here would like to be able to distinguish from the revision history of a file on trunk or a branch, which revision was used to create a tag. I'm not sure if and how this should be done. I was thinking of forcing a commit of the files somehow which creates new revisions of every file and add comment identifying the tag, before actually creating the tag. But, if the file is unchanged, commit wont work... Any ideas? Tom
Hi Tom Use the "--stop-on-copy" argument with "svn log" to determine the revision at which a branch (or tag) was copied from it's original source. For example, http://example.com/svn/tags/RELEASE-2010-02-12 was created by copying trunk to tags/RELEASE-2010-02-12, at revision "X". If you have tags/RELEASE-2010-02-12 checked out to ~/latest_release, then you could determine revision "X" by:
cd ~/latest_release svn log --stop-on-copy .I'm fairly certain other SVN clients will have similar functionality - IIRC TortoiseSVN does, for example. Mentioning "stop-on-copy" should give you enough to locate the equivalent in your client (assuming you don't use the command-line client). Cheers John
Remember what should be remembered, and forget what should be forgotten.Alter what is changeable, and accept what is mutable.
1-3 of 3
Reply to this discussion
You cannot edit posts or make replies: You should be logged in before you can post.