On Wed, Aug 22, 2007 at 03:19:23PM -0400, Erez Zadok wrote: > Thanks for the info and tips. It's a good idea of course to detect any > possible changes, but I wonder if for those of us who know what they're > doing (i.e., living on the edge :-), there could be an option to ignore > inode numbers and just depend on good 'ol ctime/mtime (as other tools like > make do). I don't think there's any need for that. You can always just run git-update-index --refresh or just git-status to refresh the stat data that's kept in the index. That miscellaneous stat data (ctime, mtime, inode number) is just there as an optimization, so git-diff doesn't have to read every file. It can be tossed out and regenerated any time. --b. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
