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

Re: Understanding move & merge

From: Lele Gaifax <lele_at_seldati.it>
Date: 2003-01-20 19:32:35 CET

>>>>> On Mon, 20 Jan 2003 10:51:07 -0500, Greg Ward <gward@mems-exchange.org> said:

    GW> I've been using Subversion for less than a week, and it's
    GW> already clear to me that file renaming has to be distinct from
    GW> copy+delete. As things stand, file renaming works *better*
    GW> with CVS than with Subversion.

Well, those are *huge* words to say :)

As it stands, given the "bugs" Karl mentioned, they have the same
behaviour from the user point of view, but at least with SVN it's not
a manual tricky hack inside the repository, and neither a dark
combination of command line options.

>>>>> On 20 Jan 2003 09:44:10 -0600, Karl Fogel <kfogel@newton.ch.collab.net> said:

    KF> It turns out that there are some complexities involved in
    KF> implementing true renames that are actually quite difficult to
    KF> deal with, so we've simply postponed dealing with it till
    KF> after 1.0.

Are those documented somewhere?

    KF> In Subversion there are still a few bugs about certain
    KF> commands not following copy history correctly

Uhm, I missed this! Am I wrong understanding this as "it's not the
copy+delete implementation that prevents this to happen, but it's a
bug in the merge command"?

thanx&bye,
lele.

-- 
nickname: Lele Gaifax	| Quando vivrò di quello che ho pensato ieri
real: Emanuele Gaifas	| comincerò ad aver paura di chi mi copia.
email: lele@seldati.it	|		-- Fortunato Depero, 1929.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jan 20 19:33:08 2003

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.