racy-git.txt: explain nsec problem in more detail
Idealists may want USE_NSEC to be the default on Linux some day. Point to a patch to better explain the requirements on filesystem code for that to happen. Signed-off-by: Jonathan Nieder <jrnieder@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Jonathan Nieder committed
Oct 9, 2009 at 05:25 UTC
989c530e7f7f85db7fb5a340319cca88ca702b2a
1 file changed
+6
-4
Documentation/technical/racy-git.txt
+6
-4
@@ -42,10 +42,12 @@ compared, but this is not enabled by default because this member
42
is not stable on network filesystems. With `USE_NSEC`
43
compile-time option, `st_mtim.tv_nsec` and `st_ctim.tv_nsec`
44
members are also compared, but this is not enabled by default
45
-because the value of this member becomes meaningless once the
46
-inode is evicted from the inode cache on filesystems that do not
47
-store it on disk.
48
-
45
+because in-core timestamps can have finer granularity than
46
+on-disk timestamps, resulting in meaningless changes when an
47
+inode is evicted from the inode cache. See commit 8ce13b0
48
+of git://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git
49
+([PATCH] Sync in core time granuality with filesystems,
50
+2005-01-04).
51
52
Racy git
53
--------