Re: [PATCH] teach update-index --refresh about --data-unchanged
- From
- Pete Wyckoff <pw@padd.com>
- Date
- Nov 3, 2010, 22:02 UTC
- Message-ID
- <20101103220243.GA6777@arf.padd.com>
- In-Reply-To
- <20101103183621.GA14019@burratino>
jrnieder@gmail.com wrote on Wed, 03 Nov 2010 13:36 -0500:
Show 15 quoted lines
> On Wed, Nov 03, 2010 at 10:37:40AM -0700, Junio C Hamano wrote: > > Pete Wyckoff <pw@padd.com> writes: > > >> When a repository has been copied with rsync, or cloned using > >> a volume manager, the index can be incorrect even though the > >> data is unchanged. This new flag tells update-index --refresh > >> that it is not necessary to reread the data contents. > > > > I know our traditional attitude towards the plumbing commands have been > > "give them long enough rope and let users hang themselves", but this > > particular rope feels a bit too long for my taste. > > Pete, I think you mentioned the possibility of a special-case tool for > contrib/ that just updates the inode, device number, and ctime fields? > That sounds a little less worrying to use, as plumbing.
Yes, I'd been discussing with Jonathan offlist that I too agree this is a bit bizarre for general use. Especially when thinking about how to explain the new flag in the manpage, and how interactions with other command-line options should work.
I wrote a short C program to use existing functions from cache.h to read and write the index, updating the entries by hand. Once I figure out how to build it nicely, I'll submit for contrib/. I haven't figured out how to include the useful bits of the top-level Makefile (like SSL setting, which SHA1, -lpthread, etc.).
-- Pete