On 19.04.2012 10:30, Thomas Bretscher wrote:
>> On 31.01.2012 15:19, Franz Hirschbeck wrote:
>>
>>> I discovered a similar problem today.
>>> Client: 1.7.4
>>>
>>> My Repo looks like this:
>>> Apps/ScanMan/ (trunk/branches/tags)
>>> ExternalLibs/UnxUtils/Release1
>>>
>>> There is a directory Apps/ScanMan/trunk/ExternalLibs with the svn:externals:
>>> ^ExternalLibs/UnxUtils/Release1 UnxUtils
>>>
>>> The log of ExternalLibs/UnxUtils/Release1:
>>> ------------------------------------------------------------------------
>>> r2745 | marcelb | 2011-03-29 18:15:22 +0200 (Di, 29 Mrz 2011) | 2 lines
>>>
>>> ExternalLibs
>>> - renamed UnxTools to UnxUtils
>>> ------------------------------------------------------------------------
>>> r2740 | marcelb | 2011-03-29 16:34:30 +0200 (Di, 29 Mrz 2011) | 2 lines
>>>
>>> ExternalLibs
>>> - added UnxTools 14-04-03
>>> ------------------------------------------------------------------------
>>>
>>> When I create a tag the dialog "Set explicit revision for these
>>> externals" has an entry for UnxUtils with the revision 2740.
>>>
>>> I expect this revision to be 2745.
> [...]
>>
>>
>> It's not really a bug: [...]
>> If you haven't updated your working copy after
>> r2745, then the external
>> your working copy is on is still on an older
>> revision [...]
>
> Hello
>
> We had a very similar problem, probably the same, I reproduced it using TSVN 1.7.6 Build 22632 - 32 Bit, before I discovered this discussion thread.
>
> Steveking says, it is not really a bug if you haven't updated your working copy. I agree so far. But in our case, we had updated our working copy, and also made several more commits in the trunk project (but no more in the external folder). Then it looks quite buggy, it's at least an unexpected behaviour.
>
> If you look at the Windows properties' SVN tab of the local WC's folder (in Franz' example: UnxUtils, which is in the repo UnxUtils/Release1), it probably shows SVN revision 2740. However, the TSVN log window of that folder probably shows rev. 2740 printed in bold, and rev. 2745 (renaming) printed normally at the top.
> I would expect the tagged externals to be set to one of the following three possibilities (again, I take the names and revs of Franz' example):
> svn:externals -r 2740 ^ExternalLibs/UnxUtils/Release1_at_2745 UnxUtils
> svn:externals -r 2745 ^ExternalLibs/UnxUtils/Release1_at_2745 UnxUtils
> svn:externals ^ExternalLibs/UnxUtils/Release1_at_2745 UnxUtils
> (the third one defaults to the same operative revision as the second one).
>
> Can the commit routine of TSVN find out such path changes and set the peg revision accordingly?
Nope, and here's why:
the revision 2745 is not part of the working copy. You can only find
that revision by contacting the repository. Now, contacting the
repository is not what we do in such dialogs because we only contact the
repo once the real command is executed. It would be very bad if suddenly
an auth dialog would pop up while you're looking at the branch/tag dialog.
Stefan
--
___
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2949932
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2012-04-19 18:45:08 CEST