You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Mathias Weinert <ma...@gfa-net.de> on 2006/02/08 08:27:02 UTC

Re: peg revision added to checkout path

Ryan Schmidt <su...@ryandesign.com> 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 �.
> 
> It's of course not difficult to avoid if you don't want it:
> 
> $ svn co -r 223 svn://myrepos/repos/trunk/olddir@223 olddir
> 

As I didn't get any more responses I now assume that this is
a bug and therefor forward it to the dev list.

Mathias

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: peg revision added to checkout path

Posted by Malcolm Rowe <ma...@farside.org.uk>.
On Fri, Feb 10, 2006 at 05:37:25PM +0000, Malcolm Rowe wrote:
> (btw, I'm also planning to commit a change to default the operative
> revision to the peg revision later on today, so that command can just be
> 'svn co svn://myrepos/repos/trunk/olddir@223'.)
> 

Done, r18422.

Regards,
Malcolm

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: peg revision added to checkout path

Posted by Malcolm Rowe <ma...@farside.org.uk>.
On Wed, Feb 08, 2006 at 05:08:54PM +0000, Julian Foad wrote:
> Mathias Weinert wrote:
> >>>>$ 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.
> >
> >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.
> 

Fixed in r18416.

(btw, I'm also planning to commit a change to default the operative
revision to the peg revision later on today, so that command can just be
'svn co svn://myrepos/repos/trunk/olddir@223'.)

Regards,
Malcolm

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: peg revision added to checkout path

Posted by Malcolm Rowe <ma...@farside.org.uk>.
On Wed, Feb 08, 2006 at 05:08:54PM +0000, Julian Foad wrote:
> Mathias Weinert wrote:
> >>>>$ 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.
> >
> >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.
> 

Fixed in r18416.

(btw, I'm also planning to commit a change to default the operative
revision to the peg revision later on today, so that command can just be
'svn co svn://myrepos/repos/trunk/olddir@223'.)

Regards,
Malcolm

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: peg revision added to checkout path

Posted by Julian Foad <ju...@btopenworld.com>.
Mathias Weinert wrote:
> Ryan Schmidt <su...@ryandesign.com> 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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: peg revision added to checkout path

Posted by Julian Foad <ju...@btopenworld.com>.
Mathias Weinert wrote:
> Ryan Schmidt <su...@ryandesign.com> 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

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org