mirror of
https://github.com/git/git
synced 2024-08-25 02:35:46 +00:00
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>
This commit is contained in:
parent
580cbb58a2
commit
989c530e7f
|
@ -42,10 +42,12 @@ compared, but this is not enabled by default because this member
|
|||
is not stable on network filesystems. With `USE_NSEC`
|
||||
compile-time option, `st_mtim.tv_nsec` and `st_ctim.tv_nsec`
|
||||
members are also compared, but this is not enabled by default
|
||||
because the value of this member becomes meaningless once the
|
||||
inode is evicted from the inode cache on filesystems that do not
|
||||
store it on disk.
|
||||
|
||||
because in-core timestamps can have finer granularity than
|
||||
on-disk timestamps, resulting in meaningless changes when an
|
||||
inode is evicted from the inode cache. See commit 8ce13b0
|
||||
of git://git.kernel.org/pub/scm/linux/kernel/git/tglx/history.git
|
||||
([PATCH] Sync in core time granuality with filesystems,
|
||||
2005-01-04).
|
||||
|
||||
Racy git
|
||||
--------
|
||||
|
|
Loading…
Reference in a new issue