Simon Large wrote:
> Stewart Bryce wrote:
>> after some further investigation (and more by luck than judgement) i
>> have discovered the real issue. issue may be a harsh word in this
>> case since i don't think that what happens is too unreasonable.
>> what i realised was that with the version checked out using the
>> subversion command line client is that the repository name had
>> so version 80's repository path is:
>> rather than the heads repository path:
>> whilst the command line client was able to realise this and check the
>> project out (albeit with all the \.svn\entries files having this in
>> url="svn://software/sdt/SysDesTool/trunk"), tortoiseSVN just wouldn't
>> let me (giving the error message shown in the first email).
>> sorry to point down the wrong path earlier. maybe tortoiseSVN should
>> warn the user that the repository path had changed between the version
>> requested and the head, but still allow the user to check it out?
>> just my opinion.
> Yes, it should if the commandline client does that. I guess we should
> also be using a peg revision if the initial request fails.
No, it shouldn't - sorry.
Yes, the CL client uses HEAD as the peg revision, while TSVN uses the
entered revision as the peg revision. The reason is simple:
with HEAD as the peg revision, you can't checkout a folder which doesn't
exist in HEAD anymore (you then have to use
svn co URL@pegrev -rRev
instead). But in TSVN, you can't enter a peg revision (try explaining
that to a user, and you know why it isn't there).
So, by using the entered rev as the peg revision, we're sure that you
can check out *any* folder which ever existed - you just have to find
out the URL it had in that revision first.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Dec 7 17:12:02 2005