Re: broken racy detection and performance issues with nanosecond file times

Am 28.09.2015 um 19:38 schrieb Junio C Hamano: > Karsten Blees writes: > >> Problem 1: Failure to detect racy files (without USE_NSEC) >> == >> >> Git may not detect racy changes when 'update-index' runs in parallel

Re: broken racy detection and performance issues with nanosecond file times

Karsten Blees writes: > Ideas for potential solutions: > == > > Performance issues: > --- > > 1. Compare file times in minimum supported precision >When comparing file times, use the minimum precision supported by >both

Re: broken racy detection and performance issues with nanosecond file times

Karsten Blees writes: > Problem 1: Failure to detect racy files (without USE_NSEC) > == > > Git may not detect racy changes when 'update-index' runs in parallel > to work tree updates. > > Consider this (where

broken racy detection and performance issues with nanosecond file times

Hi there, I think I found a few nasty problems with racy detection, as well as performance issues when using git implementations with different file time resolutions on the same repository (e.g. git compiled with and without USE_NSEC, libgit2 compiled with and without USE_NSEC, JGit executed in