[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gnu-arch-users] problem with ,,inode-sigs optimization
From: |
David Brown |
Subject: |
Re: [Gnu-arch-users] problem with ,,inode-sigs optimization |
Date: |
Mon, 15 Sep 2003 22:35:42 -0700 |
User-agent: |
Mutt/1.5.4i |
On Tue, Sep 16, 2003 at 02:11:25PM +0900, Miles Bader wrote:
> (2) Don't keep per-revision state at all, just keep single per-version
> state-file in ,,inode-sigs. It would be slightly incorrect for
> queries against older revisions, but that shouldn't matter, since
> it will just cause a cache miss for those few files that are
> different in older revisions (which usually isn't very many); it
> doesn't seem like it could result in incorrect behavior.
It also might be handy to be able to reset the info once it is determine
that a file is, in fact, identical. This would be the case if someone
edits a file, and then undoes the changes, and writes the result out.
Or a common scenario I do:
- Delete all of the source files.
- Extract a tar file of the next version of the distribution.
- tree-lint, inventory, and what-changed to find out what happened.
Many of these files will remain the same, even though their inodes are
now different.
Dave
- [Gnu-arch-users] problem with ,,inode-sigs optimization, Miles Bader, 2003/09/16
- Re: [Gnu-arch-users] problem with ,,inode-sigs optimization,
David Brown <=
- [Gnu-arch-users] Re: problem with ,,inode-sigs optimization, Miles Bader, 2003/09/16
- [Gnu-arch-users] Re: problem with ,,inode-sigs optimization, Miles Bader, 2003/09/16
- Re: [Gnu-arch-users] problem with ,,inode-sigs optimization, Tom Lord, 2003/09/16