From: Andreas Schwab <schwab@linux-m68k.org>
To: Mark Hills <mark@xwax.org>
Cc: git@vger.kernel.org
Subject: Re: Consist timestamps within a checkout/clone
Date: Mon, 31 Oct 2022 21:17:08 +0100 [thread overview]
Message-ID: <878rkvychn.fsf@igel.home> (raw)
In-Reply-To: <2210311614160.25661@stax.localdomain> (Mark Hills's message of "Mon, 31 Oct 2022 19:01:20 +0000 (GMT)")
On Okt 31 2022, Mark Hills wrote:
> It's entirely possible there's _never_ a guarantee of consistency here.
I don't think the order in which git writes the individual files is
defined in any way. Thus depending on the precision of the time stamps
in the file system whether a file ends up newer than another one may
vary each time due to timing differences.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something completely different."
next prev parent reply other threads:[~2022-10-31 20:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 19:01 Consist timestamps within a checkout/clone Mark Hills
2022-10-31 20:17 ` Andreas Schwab [this message]
2022-10-31 20:21 ` Ævar Arnfjörð Bjarmason
2022-10-31 20:36 ` Taylor Blau
2022-10-31 22:31 ` Mark Hills
2022-10-31 22:42 ` rsbecker
2022-11-01 18:34 ` Ævar Arnfjörð Bjarmason
2022-10-31 22:29 ` Mark Hills
2022-11-01 17:46 ` Ævar Arnfjörð Bjarmason
2022-11-02 14:16 ` Matheus Tavares
2022-11-02 14:28 ` Matheus Tavares
2022-11-01 13:55 ` Marc Branchaud
2022-11-02 14:45 ` Ævar Arnfjörð Bjarmason
2022-11-03 13:46 ` Marc Branchaud
2022-11-01 14:34 ` Erik Cervin Edin
2022-11-01 15:53 ` Ævar Arnfjörð Bjarmason
2022-11-03 13:02 ` Erik Cervin Edin
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=878rkvychn.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=mark@xwax.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.