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

Re: Caching text-size in the entries file

From: Ph. Marek <philipp.marek_at_bmlv.gv.at>
Date: 2006-09-27 07:43:18 CEST

On Tuesday 26 September 2006 07:56, Peter Samuelson wrote:
> [Erik Huelsmann]
> > I started working on a patch to record the size of the (unedited)
> > working copy file in the entries file. Using 1 stat() call and this
> > value, we can detect whether the working copy file has changed,
> > without the need to detranslate.
> If you're adding fields to the entries file anyway, with the aim of
> independence from mtimes, I suggest an inode number field too. (Yes,
> apr makes an inode number available on win32 as well as unix). The
> idea is to require the inode number to match, as well as the mtime,
> when deciding to skip the file compare.
I don't think that will help.

> This prevents a misunderstanding with 'svn update foo1 foo2; mv foo1
> foo2'. (The 'svn update' will give foo1 and foo2 approximately the
> same mtime, and 'mv' does not change it, so at present this will not
> detect that foo2 has changed.)
What about the use-case
        cp -a foo1 foo2
        (edit foo1)
        (find that changes are bad)
        mv foo2 foo1
That wouldn't change the data, but the inode.

I believe that scenario has about the same usage probability as yours, given
that foo1 and foo2 have to have the same size :-)



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Sep 27 07:43:38 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.