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

svn up should *fail* on working copy whose source url correspond to some other node?

From: Kamesh Jayachandran <kamesh_at_collab.net>
Date: Thu, 14 Aug 2008 20:54:45 +0530

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi All,

I deleted issue-2897-take2 branch at r32477 and recreated again it from
trunk_at_32477 at r32478. When I ran 'svn up' on my old 'issue-2897-take2'
working copy it updated to the new URL which I think is wrong or atleast
a new behaviour in trunk.

$trunk_svn co
http://svn.collab.net/repos/svn/branches/issue-2897-take2@32476

$cd issue-2897-take2
$trunk_svn up #This should fail, but succeeds as of trunk svn

Any thoughts?

With regards
Kamesh Jayachandran
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIpE483WHvyO0YTCwRAmFJAJ9jRhH1btaBnTdKZKKcyw9E/UYItgCfTMv9
/TMncq7FZUGFSGxOq7XLcfo=
=2gfP
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-08-14 17:25:58 CEST

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.