You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Hans Marggraff <hm...@qint.de> on 2003/05/02 09:18:08 UTC

error message using revision named FIRST

I applied the following checkout command to
a branch:

     C:\J\tst3>svn co -r FIRST http://dino.qint.de/repos/testsvnup/branches/b2 .

And got the following error message:
     svn: RA layer request failed
     svn: PROPFIND of /repos/testsvnup/!svn/bc/0/branches/b2: 404 Not Found

I had hoped to get the revision when the branch was created. Revision
0 is obvoiusly useless, because it cant exist in the branch.

In the current implementation FIRST is hard coded as rev 0 which is rather
uninteresting.

If FIRST pointed to the first revision of the branch, then merging would be easier
because this is the revision that is frequently used for merging from.

Regards

-- 
Hans Marggraff
Qint Software
Allingerstr. 18a
82178 Pucheim
Germany
Tel 089 80067094
mailto:hmf@qint.de
http://www.qint.de


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

Re: error message using revision named FIRST

Posted by Ben Collins-Sussman <su...@collab.net>.
Hans Marggraff <hm...@qint.de> writes:

> In the current implementation FIRST is hard coded as rev 0 which is rather
> uninteresting.
> 
> If FIRST pointed to the first revision of the branch, then merging
> would be easier because this is the revision that is frequently used
> for merging from.

Yes, and someday when svn implements 'merge tracking', it will
remember these things -- not only revs in which branches were created,
but also exactly which sets of revs get merged.

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