On 18:03 Fri 15 Jul, Robin H. Johnson wrote: > Hi all, > > In tracing down problems with the git->rsync path, it has been noticed > that some developers have significant clock drift on their local systems > (up to one case of 14 days wrong), and it's potentially contributing to > problems in generating the rsync tree. > > I have implemented a check as part of the hook that validates Git push > certificates (require-signed-push). It looks for clock drift or an > overly long push, and aborts if needed. > > The tolerances are presently set to: > - 5 seconds of clock drift. > - 'git push' must be completed in 60 seconds.
AFAIR Windows AD servers allow 5 minutes clock drift. How about at least a minute or so?
