* Incorrect time on different machines = file changes loss.
@ 2012-05-12 12:12 Oleg Serov
2012-05-12 12:55 ` Carlos Martín Nieto
0 siblings, 1 reply; 2+ messages in thread
From: Oleg Serov @ 2012-05-12 12:12 UTC (permalink / raw)
To: git
Please add local and server time difference check when happing pull or push.
Incorrect time on different machines = file changes loss.
Thanks!
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Incorrect time on different machines = file changes loss.
2012-05-12 12:12 Incorrect time on different machines = file changes loss Oleg Serov
@ 2012-05-12 12:55 ` Carlos Martín Nieto
0 siblings, 0 replies; 2+ messages in thread
From: Carlos Martín Nieto @ 2012-05-12 12:55 UTC (permalink / raw)
To: Oleg Serov; +Cc: git
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
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-05-12 12:55 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-05-12 12:12 Incorrect time on different machines = file changes loss Oleg Serov
2012-05-12 12:55 ` Carlos Martín Nieto
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).