From: "Carlos Martín Nieto" <cmn@elego.de>
To: Oleg Serov <serovov@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Incorrect time on different machines = file changes loss.
Date: Sat, 12 May 2012 14:55:05 +0200 [thread overview]
Message-ID: <1336827305.3002.22.camel@centaur.lab.cmartin.tk> (raw)
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
prev parent reply other threads:[~2012-05-12 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
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 message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1336827305.3002.22.camel@centaur.lab.cmartin.tk \
--to=cmn@elego.de \
--cc=git@vger.kernel.org \
--cc=serovov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).