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

Re: Proposal: Genuine renames/moves within the WC.

From: Philip Martin <philip_at_codematters.co.uk>
Date: 2005-01-12 19:24:16 CET

"Oliver Klozoff" <stevieoh@fastmail.fm> writes:

>> "Oliver Klozoff" <stevieoh@fastmail.fm> writes:
>> > However, entries with the 'moved' attribute *should* be allowed to
>> > move again, so that this:
>> >
>> > # [case 2]
>> > $ svn mv a b
>> > $ svn mv b c
>> You don't need to add a 'moved' attribute to implement that,
>> in fact it would be wrong to do so because there is no reason
>> not to support
>> $ svn copy a b
>> $ svn mv b c
> Okay, now consider this situation:
> $ svn cp adir bdir
> $ svn mv bdir/afile ./afile
> $ svn commit afile
> What are we supposed to do now?

First, it doesn't affect the point of my previous mail, namely that
support for "svn cp/mv a b" followed by "svn mv b c" does not need a
new attribute.

As far as handling your new scenario, I guess it depends whether you
accept the that new afile should have copyfrom history that comes from
the original adir/afile rather than from the transient bdir/afile.
Assuming you do accept that, then I think that once again it can be
implemented without the need for a new attribute.

I'm not arguing that there is no need for the new attribute, I'm just
pointing out that some of the enhacements that have been discussed do
not require it.

Philip Martin
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 12 19:26:05 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.