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

Re: [Issue 2746] New - update overwrites w/o warning local modification if local timestamp did not change

From: Erik Huelsmann <ehuels_at_gmail.com>
Date: 2007-03-24 17:22:00 CET

On 3/23/07, Greg Hudson <ghudson@mit.edu> wrote:
> On Wed, 2007-03-21 at 21:49 +0100, Erik Huelsmann wrote:
> > Ben Reser tells me ctime updating can be turned off on many
> > filesystems and many admins seem to do so.
> That comment sounds confused. You can turn off atime updating for
> performance and many people do; there's no reason I know of to turn off
> ctime updating.
> There does seem to be a real issue here:
> svn update
> mv file1 file2 # file1 has same size and mtime as file2
> svn rm file1
> svn st # file2 appears unchanged
> svn update # Smashes file2
> It may be an uncommon case, but there's no broken tool involved, and
> mv's behavior isn't going to change.

Right, but with trunk, these files will also have to have the same
size, because that's now part of the heuristic. (Not sure whether you
follow development that close.)

> I agree that all proposed solutions have serious drawbacks. Using ctime
> means working copies become slow after a filesystem backup, until
> cleanup is run. Using inodes mean working copies become slow after a
> copy operation (even a well-executed one which preserves mtimes), until
> cleanup is run. Doing a full compare all the time means working copies
> are always slow.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Mar 24 17:22:14 2007

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.