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

Re: Moving and copying multiple targets

From: Michael Sinz <Michael.Sinz_at_sinz.org>
Date: 2005-11-15 15:38:51 CET

On 11/14/05, Hyrum K. Wright <hyrum_wright@byu.edu> wrote:
> So, I've finally spent a few minutes to investigate what it would take
[...]
> In the client application, the add command does *not* push multiple
> targets at once down to the client library. It simply loops over each
> file to be added and makes a separate call to the client library. It
> was pointed out that for move, this is *not* preferred; what about add?
[...]

I think the main difference here is that there are different target types
which makes for vastly different logical and physical behaviors.

svn add *always* works on the working copy. Thus the whole atomic
commit feature is not an issue as the commit happens after the fact.

svn move/copy *sometimes* works on the working copy and sometimes
works directly on the target repository. There are significant differences
between the two behaviors.

svn move/copy within the working copy can (and, IMHO, should) work
rather easily via multiple calls to the library. The svn commit that
happens later will make sure all of the needed items are atomic with
respect to the repository.

Supporting svn move/copy to destination URLs is a whole different ball
of wax since the destination is, by definition, a repository and thus
the whole action wishes to be atomic.

From my point of view, I would first support the multiple source to WC
target since the behavioral semantics are fully understood and the
issue of atomic action is handled externally via svn commit.

I understand the wish to support the direct use of a repository. There
are times it really would be useful. However, I would not hold back
the multi-source move/copy support within a WC just because of
the wish to support a URL target. I can see this as being a rather
difficult problem that, as far as I can see, will require server changes.

--
Michael Sinz               Technology and Engineering Director/Consultant
"Starting Startups"                          mailto:Michael.Sinz@sinz.org
My place on the web                      http://www.sinz.org/Michael.Sinz
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 15 15:40:52 2005

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.