diff options
| author | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-05-22 15:08:15 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@ppc970.osdl.org> | 2005-05-22 15:08:15 -0700 |
| commit | 2cb45e95438c113871fbbea5b4f629f9463034e7 (patch) | |
| tree | 010a767b55ccb6b44c73024ab1fb8de536c5137c /Makefile | |
| parent | 09d74b3b5ac634495e17b92b2b785fa996ffce97 (diff) | |
| download | git-2cb45e95438c113871fbbea5b4f629f9463034e7.tar.gz | |
Don't care about st_dev in the index file
Thomas Glanzmann points out that it doesn't work well with different
clients accessing the repository over NFS - they have different views
on what the "device" for the filesystem is.
Of course, other filesystems may not even have stable inode numbers.
But we don't care. At least for now.
Diffstat (limited to 'Makefile')
| -rw-r--r-- | Makefile | 4 |
1 files changed, 3 insertions, 1 deletions
@@ -2,7 +2,9 @@ # 1461501637330902918203684832716283019655932542976 hashes do not give you # enough guarantees about no collisions between objects ever hapenning. # -# -DNSEC if you want git to care about sub-second file mtimes and ctimes. +# -DUSE_NSEC if you want git to care about sub-second file mtimes and ctimes. +# -DUSE_STDEV if you want git to care about st_dev changing +# # Note that you need some new glibc (at least >2.2.4) for this, and it will # BREAK YOUR LOCAL DIFFS! show-diff and anything using it will likely randomly # break unless your underlying filesystem supports those sub-second times |