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

[RFC PATCH 0/1] Canonical tar format for Git

From
brian m. carlson <sandals@crustytoothpaste.net>
Date
Feb 5, 2023, 22:17 UTC
Message-ID
<20230205221728.4179674-1-sandals@crustytoothpaste.net>

With recent discussions about guaranteeing some stability for our archives, here's a document which specifies a canonical tar format we can use, based on the pax format.

It contains a sufficient amount of explanation about how the format works to (hopefully) be easily understandable, and it explains the benefits of the extremely rigid format it defines.

If we decide that we'd like to implement extensions to it in the future, it can be easily extended. My original approach allowed specifying version extensions to specify that things like permissions or timestamps were persisted, but I simplified for ease of use, since we don't technically need those changes.

Feedback about this approach is welcome, and after some discussion, I plan to send a future version with an actual implementation and tests.

brian m. carlson (1):
  Document a fixed tar format for interoperability
 Documentation/technical/tarball.txt | 234 ++++++++++++++++++++++++++++
 1 file changed, 234 insertions(+)
 create mode 100644 Documentation/technical/tarball.txt
Next: brian m. carlson
Message 1 of 9 in “Canonical tar format for Git”
  1. 0/1 Canonical tar format for Gitbrian m. carlson, Feb 5, 2023
  2. 1/1 Document a fixed tar format for interoperabilitybrian m. carlson, Feb 5, 2023
  3. Junio C HamanoFeb 6, 2023
  4. brian m. carlsonFeb 7, 2023
  5. Ævar Arnfjörð BjarmasonFeb 6, 2023
  6. brian m. carlsonFeb 7, 2023
  7. Ævar Arnfjörð BjarmasonFeb 8, 2023
  8. brian m. carlsonFeb 8, 2023
  9. Ævar Arnfjörð BjarmasonFeb 9, 2023

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.