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

Re: svn copy onto itself is possible

From: mark benedetto king <mbk_at_lowlatency.com>
Date: 2003-10-01 16:38:34 CEST

On Wed, Oct 01, 2003 at 09:16:48AM -0500, Ben Collins-Sussman wrote:
> "C. Michael Pilato" <cmpilato@collab.net> writes:
>
> > Ben Collins-Sussman <sussman@collab.net> writes:
> >
> > > Hm, oh well. I find Unix 'cp' behavior really intuitive, and I don't
> > > think I've ever been bitten by this, in Unix or Subversion. Maybe I'm
> > > just a freak. :-)
> >
> > You've never, ever, tried to use 'mv' to rename DIR1 to DIR2 unaware
> > that there already was a DIR2 on your system? As universally as you
> > use 'foo', 'bloo', et al, I find that really hard to believe -- but
> > hey, I'll give you the benefit of the doubt.
>
> I think it's because I'm always super-paranoid using Unix or svn
> 'mv'. I manually check the destination beforehand. I double-check
> the commandline. These behaviors are now ingrained.
>
> So, hmmm.... perhaps such excessive paranoia *is* indicative of a UI
> problem. Maybe a warning would be kinder. :-)

Also: while it's usually reasonably safe to assume exclusive access
to a filesystem ("this is my home directory; hopefully no one else
has access to it"), the assumption is less safe for a centralized
repository.

The potential for races is significant; for example, both Anne and
Bob might realize that a certain branch needs to be created at the
same time, both might check to make sure it doesn't already exist,
and then both might try to create the branch. One will create the
branch. The other will create a subdirectory in the branch.

--ben

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Oct 1 16:40:32 2003

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.