|
From: | Aaron Bentley |
Subject: | Re: [Gnu-arch-users] Re: tla on nfs only |
Date: | Sun, 14 Mar 2004 22:36:01 -0500 |
User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031221 Thunderbird/0.4 |
Stefan Monnier wrote:
I think the core of the problem is that too many files of the revlib are checked every time. If tla were more careful to only check the files it actually looks at, then it would have much more freedom to use other kinds of checks that don't depend on inode or device numbers.See my last email. In order to know which files changed, we must check all of them.I'm not sure which email you're referring to.
===To compute a changeset using "changes", you need to compare every file against something. Typically, we check against the inode signatures as a shortcut, but if that doesn't work, we fall back to checking against the revision library or pristine. In that case, (i.e. YOUR case) we need to check every file in the tree.
===
But you're not talking about the same thing as I am. I'm talking about revlibs where checking is done only to detect corruption.
Obviously we do not need to check for corruption of file FOO if FOO will not be read in the course of the current operation.
Yes. Unfortunately, we don't know which files in the working directory have changed until we look at the revision library. In that case, we need ALL the files in the revlib to be uncorrupted.
Aaron
[Prev in Thread] | Current Thread | [Next in Thread] |