[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn commit: rev 2024

From: <sussman_at_collab.net>
Date: 2002-06-05 19:38:59 CEST

From: Ben Collins-Sussman <sussman@collab.net>
Date: 05 Jun 2002 12:38:53 -0500
In-Reply-To: <20020529005651.A2243@raven.inka.de>
Message-ID: <86lm9tr5g2.fsf_-_@kepler.ch.collab.net>
Lines: 40
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1.50
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

Hey Josef, are you still experiencing this bug with today's svn?

Josef Wolf <jw@raven.inka.de> writes:

> On Tue, May 28, 2002 at 04:19:36PM -0500, kfogel@tigris.org wrote:
> > Author: kfogel
> > Date: 2002-05-28 21:18 GMT
> > New Revision: 2024
> > [ ... ]
>
> Ough! This one seems to break "svn cp" on my machine:
>
>
> $ cd /tmp/subvers.test
> $ svnadmin create rep
> $ mkdir -p test/trunk test/branches test/tags
> $ echo 1st version >test/trunk/x
> $ svn import -m 'first revision' file:///tmp/subvers.test/rep test
> Adding ./trunk
> Adding ./trunk/x
> Adding ./branches
> Adding ./tags
> Transmitting file data .
>
> Committed revision 1.
> $ svn cp -m 'tag it' file:///tmp/subvers.test/rep/trunk file:///tmp/subvers.test/rep/tags/V1.0
>
> /home/jw/local/l/subvers/src/svn/subversion/libsvn_client/copy.c:162
> svn_error: #21044 : <Can't find a working copy path>
> error decomposing relative path `trunk'
>
>
> This worked as expected with r2023. Is this a known thing? or do I use
> "svn cp" the wrong way?
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: svn-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: svn-help@subversion.tigris.org

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jun 5 19:41:34 2002

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.