From: Linus Torvalds <torvalds@osdl.org>
To: Andreas Ericsson <ae@op5.se>
Cc: Aubrey <aubreylee@gmail.com>, git@vger.kernel.org
Subject: Re: Quick question: how to generate a patch?
Date: Mon, 27 Feb 2006 09:28:37 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0602270923120.22647@g5.osdl.org> (raw)
In-Reply-To: <44033241.6070001@op5.se>
On Mon, 27 Feb 2006, Andreas Ericsson wrote:
>
> Did you by any chance do chmod -R, chown -R or start an ntp daemon somewhere
> in between there (don't know if clock skews will be detected by git, but...)?
off on this tangent: git shouldn't care about clock skew, because git
never cares about the current time. The only thing that matters is that
"stat()" returns the same time when called sequentially.
Now, if you have a distributed filesystem, and the _filesystem_ has some
strange clock-skew problem, that would definitely screw up git.
That sounds insane, but a trivial case of it might be a networked
filesystem where the mtime/ctime for a file create is filled in by the
client first, but then the server will do the "final version" when it
actually writes the file.
We used to have some bugs in our NFS client that did things like that: the
"mtime" of a file had this confusing duality between "client time" and
"server time", and it depended on whether the client had done a "getattr"
to the server which one you saw.
I could well imagine that we still have some bug like that (ctime in
particular is much less used than mtime, and thus more likely to have not
been noticed). And it could be much worse on some less-commonly-used and
less-unixy networked filesystem like smb, which is why I was wondering
what OS version and filesystem Aubrey might be using.
Linus
next prev parent reply other threads:[~2006-02-27 17:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-27 14:57 Quick question: how to generate a patch? Aubrey
2006-02-27 15:28 ` Andreas Ericsson
2006-02-27 16:04 ` Linus Torvalds
2006-02-27 16:18 ` Aubrey
2006-02-27 16:32 ` Linus Torvalds
2006-02-27 17:02 ` Aubrey
2006-02-27 17:09 ` Andreas Ericsson
2006-02-27 17:18 ` Aubrey
2006-02-27 17:28 ` Linus Torvalds [this message]
2006-02-28 1:55 ` Aubrey
2006-02-28 2:09 ` Linus Torvalds
2006-02-28 2:48 ` Aubrey
2006-02-27 17:19 ` Linus Torvalds
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=Pine.LNX.4.64.0602270923120.22647@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=ae@op5.se \
--cc=aubreylee@gmail.com \
--cc=git@vger.kernel.org \
/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).