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

Re: Why --force with mv?

From: Jack O'Quin <joq_at_io.com>
Date: 2004-12-21 15:57:43 CET

Ben Collins-Sussman <sussman@collab.net> writes:

> On Dec 20, 2004, at 11:23 PM, Jack O'Quin wrote:
>>
>> I think he's suggesting that since the user has made a copy the
>> modified working file, nothing really gets lost. So, the `rm' part of
>> the `mv' operation could probably just assume the --force option in
>> that case. Conceptually, `svn mv' == `svn cp && svn rm --force'.
>> Since the copy must succeed before doing the remove, that should be
>> safe enough (AFAICT).
>
> Ahh, that's a good idea! Maybe post the idea to dev@ as a enhancement
> request?

I'm a subversion newbie, not on dev@ yet. (Fine program, BTW!)

If you think it worth suggesting, either you or Anthony should post it
there. I ran into something similar in my early experiments with SVN.
It *was* rather confusing.

-- 
  joq
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Dec 21 15:58:51 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.