threads / discuss / 30521

Incorrect time on different machines = file changes loss.

Subject: Incorrect time on different machines = file changes loss.

## tl;dr

2 messages between May 12, 2012 and May 12, 2012.

replies: 1people: 2as markdown or json

Carlos Martín Nieto· May 12, 2012, 12:55 UTC · re: Oleg Serov · lore

Re: Incorrect time on different machines = file changes loss.

On Sat, 2012-05-12 at 16:12 +0400, Oleg Serov wrote:
> Please add local and server time difference check when happing pull or push.
> 
> Incorrect time on different machines = file changes loss.
 Care to explain what this means? What did you do? What happened? What
should have happened? What part of the fetch or push relies on time and
would break if one of the clocks is wrong?
 The data exchange protocol never speaks about time, and git primarily
uses the commit graph in order to determine what to do. Some
optimisation is done with timestamps in e.g. tag --contains but this
shouldn't affect the operations you say are wrong.
   cmn

← back to recent threads