Re: peg revision added to checkout path
Julian Foad <[email protected]> Wed, 08 Feb 2006 17:08:54 +0000
| Newsgroups | gmane.comp.version-control.subversion.devel,gmane.mail.eyebrowse.user |
|---|---|
| Message-ID | <43EA25A6.6010006__11720.6602859826$1139418934$gmane$org@btopenworld.com> |
Mathias Weinert wrote: > Ryan Schmidt <[email protected]> wrote: >>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@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 �. > > As I didn't get any more responses I now assume that this is > a bug and therefor forward it to the dev list. Yes, it's a bug. Thanks for the report. - Julian