git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: force deterministic trees on git push - exact sort-order of filenames

From
Junio C Hamano <gitster@pobox.com>
Date
Oct 18, 2021, 05:38 UTC
Message-ID
<xmqq7deazydf.fsf@gitster.g>
In-Reply-To
<87ilxvd3uw.fsf@evledraar.gmail.com>
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> I suppose there could be more strictures in the fsck code to allow for
> that use-case, but still make some things that are mere warnings now
> hard errors (or "fatal").

There is a group of configuration variables fsck.* to let you pass specific types of errors go without erroring out on them, and also fsck.skiplist lets you ignore errors on specific objects, but both need to ask people on the other side to flip them on.

I'd imagine that hosting providers can make it self-service for repository owners, though, but if they employ shared object store across repositories, it might become a bit cumbersome to implement correctly.

Previous: Ævar Arnfjörð Bjarmason
Message 6 of 6 in “force deterministic trees on git push - exact sort-order of filenames”
  1. milan hauthOct 15, 2021
  2. René ScharfeOct 15, 2021
  3. Junio C HamanoOct 15, 2021
  4. milan hauthOct 15, 2021
  5. Ævar Arnfjörð BjarmasonOct 17, 2021
  6. Junio C HamanoOct 18, 2021

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.