RE: question clarification needed (tagging with embedded externals)
From: Bob Archer <bob.archer_at_amsi.com>
Date: Wed, 29 Jul 2009 11:25:20 -0400
Ok,
So after you put the /Release folder and the .msi file into your WC you do an TSVN -> ADD?
Then you do the tag from WC then you revert the WC?
Is that the steps you are taking? I'm just trying to understand. I was not aware you could do that. It's pretty slick way to do it, I must admit.
BOb
From: Robin Guest [mailto:robin.guest_at_gmail.com]
2009/7/28 Bob Archer <bob.archer_at_amsi.com<mailto:bob.archer_at_amsi.com>>
Interesting. Are you saying that when you tag from working copy files that are not in svn are added to the tag? I didn't know that would happen.
http://img196.imageshack.us/img196/6310/tagfromwc.png
The first Added action is the base tag. It's chosen r1720 as the tag point, I think, because this is the last change to any of the four externals.
The Replacing actions are all the files already in trunk that were revised since 1720.
The Modified action is the locally modified and pegged svn:externals property, which contains all four externals, like this:
^/Common/Components/AutoUpgradeAPI/trunk/API_at_1747 AutoUpgradeAPI
The last two Added actions are the installer that was Added in the wc only.
The results look quite complicated when you analyse them like that, but creating the tag is simple and "just works", every time!
------------------------------------------------------
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
|
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.