Yann Dirson wrote: > Yes, it happens systematically when copying a git tree, even with "cp > -a" - presumably a consequence of stat granularity.
Oh, ok --- that's expected. It's the inode numbers, ctime, etc. See [1] for a partial explanation. Unlike "make", git really wants the stat information it looks at to be a completely valid cache key and since cp or rsync with some options might leave out some information git cares about (e.g. executable bit), git does need a refresh in that case. Thanks again for the prodding before. Jonathan [1] http://thread.gmane.org/gmane.comp.version-control.git/89370/focus=89993 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
