Re: peg revision added to checkout path

On Feb 6, 2006, at 11:59, Mathias Weinert wrote:

>> I found something which first seems to be bug for me. I am not
>> sure if I even already read about it but at least I didn't find
>> anything in the issue tracker. But after thinking a while it
>> might also be a feature. So here comes the description:
>>
>> I want to check out a path that doesn't exist any more so I use
>> a peg revision. Unfortunately Subversion uses the @-suffix to
>> build the working copy path name if I don't provide one:
>>
>> $ svn co -r 223 svn://myrepos/repos/trunk/olddir_at_223
>> A olddir@223/file2.txt
>> A olddir@223/newdir
>> A olddir@223/branchfile.txt
>> Checked out revision 223.
>>
>> This happens with Subversion 1.3.0 under cygwin as well as when
>> I use the win32 binaries.
>>
>> As already said: is this a bug or a feature?
>
> Any ideas or comments to the following post I made on 01/25?

My personal feeling is that this is a bug. Just my 0.02 €.

It's of course not difficult to avoid if you don't want it:

$ svn co -r 223 svn://myrepos/repos/trunk/olddir_at_223 olddir

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Feb 6 12:32:32 2006