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

Re: Make --force always switched on for svn move command (was Re: [PATCH] Moving/copying added files and dirs)

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2006-08-11 18:26:59 CEST

On 8/9/06, Ivan Zhakov <chemodax@gmail.com> wrote:
> On 8/9/06, Ivan Zhakov <chemodax@gmail.com> wrote:
> > On 8/9/06, Paul Burba <paulb@softlanding.com> wrote:
> > > Notice none of the unversioned children of H get moved, while only A\D\I
> > > gets copied.
> > >
> > > Also, a related oddity: While svn copy normally copies these first
> > > generation unversioned children, svn move requires you to use --force and
> > > then it *deletes* all the unversioned items in the source and does *not*
> > > copy any of them...so much for "this subcommand is equivalent to a 'copy'
> > > and 'delete'."
> > >
> > You are not right, they copied, but doesn't displayed in svn st -v.
> > Just check directory D_move\I by hand.
> >
> >
> BTW, is anybody know reasons why we forbidd move directories with
> unversioned files without --force option? I consider we should allow
> this, because we are copying *all* files including unversioned at new
> location. Might be we don't need treat this situation as dangerous and
> perform operation without user attention?

As long as we're always copying the unversioned files, that makes sense to me.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Aug 11 18:28:49 2006

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.