git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Carlos Martín Nieto <cmn@elego.de>
Date
May 12, 2012, 12:55 UTC
Message-ID
<1336827305.3002.22.camel@centaur.lab.cmartin.tk>
In-Reply-To
<CAMkKa8D0+9M8QF51r_5kPx19rQMKh+8oXs7z9dtSLkfb=a2MtQ@mail.gmail.com>
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
Previous: Oleg Serov
Message 2 of 2 in “Incorrect time on different machines = file changes loss.”
  1. Oleg SerovMay 12, 2012
  2. Carlos Martín NietoMay 12, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.