On 7/24/2013 3:34 PM, Stefan Küng wrote:
> On 24.07.2013 21:29, Ben Johnson wrote:
>> On 7/24/2013 3:15 PM, Stefan Küng wrote:
>>> That's by design:
>>> The revision you see there is the revision the external was last updated
>>> to, not it's last committed revision.
>>>
>>> Stefan
>>
>> Thanks for the quick reply, Stefan. Also, thank you for all of the work
>> that you have put into TSVN. I'm amazed at how much you accomplish as a
>> single human being. :)
>>
>> Glad to learn that this is not a bug. I'm trying to digest the
>> implications of this change.
>>
>> In the past, I have used the Branch/Tag dialog to discern certain
>> externals' revision numbers, just so I could peg them manually (since
>> there is no way to peg some or all externals at specific revisions, en
>> masse, within TSVN). As an aside, you may recall that you created a
>> Feature Request on my behalf to address this need a couple of weeks ago.
>>
>> With TSVN 1.8.x, what is the equivalent method for doing what I describe
>> above? I assume that I would not want to peg all of my externals at the
>> revision number listed there (1224, per the example in my O.P.).
>
> But that's what you should do: you updated the externals to that
> revision, so you should peg it to that revision.
>
I suppose that my confusion stems from the fact that some of these
externals don't even have revision numbers as high as 1224 (1224 is the
highest revision of only one of the externals). Suppose that an external
repository only has 10 revisions, and suppose that I want to prevent any
revision greater than 5 from being pulled into my working copy when I
update. It "feels" like I would need to manually enter the number 5
somewhere for that to happen.
> Problem with the previous approach was (using the last-committed
> revision) that if you renamed/moved a file in the externals, that
> wouldn't increase the last-committed revision of the file and therefore
> you would peg to a revision before that rename/move.
Hmm, I seem to be misunderstanding something fundamental, because I
thought that the scenario you describe above is exactly why one would
want to peg externals at a last-committed revision number. If I
rename/move a file in an external after I've pegged said external at a
specific revision number in the main repo, and then I update my working
copy, I don't want that renamed/moved file being pulled into my working
copy.
> Using the revision the external was last updated to is the safe way to
> do it.
>
>> Is it now necessary to discern the correct revision number at which to
>> peg each external using the Properties dialog's Subversion tab, under
>> the "Last changed revision" field?
>
> No, just use the revision that's shown there.
>
Just to reiterate, this is confusing to me. If all externals show 1224
in that dialog (even though many of them have far fewer revisions in
total), and I peg all externals at revision 1224, what's to stop new
changes from being pulled into my working copy when I update?
To be clear, the main repository has something like 210 revisions. The
1224 that is being displayed seems to be the highest revision number of
any of the externals that are defined within the project. I'm not sure
why that external, in particular, is the one whose highest revision
number is displayed in this dialog.
> Stefan
>
I'm not trying to be difficult, and needless to say, you have more than
proven your knowledge and understanding of SVN. I'm just trying to
educate myself so that those who depend on my advice are able to make
informed decisions.
Thanks again, Stefan,
-Ben
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3061290
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2013-07-25 16:21:42 CEST