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

Incorrect behaviour on wc copy when using checkout/update --depth

From: Chris Rose <chris.rose_at_messagingdirect.com>
Date: Sun, 13 Jan 2008 15:50:25 -0700

The short description is this:

If I check out a working copy without taking all of its children (say,
with depth=empty, or depth=files etc...) then when I copy it into
another part of the working copy that restriction should propagate:

% svn co --depth=empty $url/trunk/foo

% svn co $url/tags

% svn cp foo tags/foo_tagged

% ls tags/foo_tagged

% svn ci -m "Tagged an empty copy of 'foo'" tags

% svn co $url/tags/foo_tagged

% ls foo_tagged
  <everything that was in foo on the trunk>

Attached is a script that demonstrates the issue in detail. It
requires svn 1.5, because --depth is a new thing :)

I contend that checking in a working copy that does not have files,
and then checking the same URL out to find out that it does have files
violates the principle of least surprise. However, it would probably
be enough to provide an option to preserve checkout depth on copy.

To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org

Received on 2008-01-13 23:50:41 CET

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