mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Duy Nguyen <>
To: "Ævar Arnfjörð Bjarmason" <>
Cc:, Git Mailing List <>
Subject: Re: Are clone/checkout operations deterministic?
Date: Tue, 17 Jul 2018 20:06:44 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, Jul 17, 2018 at 11:50 AM Ævar Arnfjörð Bjarmason
<> wrote:
> In practice I think clone, checkout, reset etc. always work in the same
> order you see with `git ls-tree -r --name-only HEAD`, but as far as I
> know this has never been guaranteed or documented, and shouldn't be
> relied on.
> E.g. there's probably cases where writing files in parallel is going to
> be faster than writing them sequentially. We don't have such a mode just
> because nobody's written a patch for it, but having that patch would

Well I did have some patches [1] but as usually I did not follow
through. Interestingly there's actually concern about timestamp order
[2] even back then


> break any assumptions of our current order.

  parent reply	other threads:[~2018-07-17 18:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-17  9:14 Are clone/checkout operations deterministic? J. Paul Reed
2018-07-17  9:48 ` Ævar Arnfjörð Bjarmason
2018-07-17 17:58   ` Stefan Beller
2018-07-17 18:06   ` Duy Nguyen [this message]
2018-07-17 19:52   ` Jeff King

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).