From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: <git@vger.kernel.org>
Cc: "Eli Schwartz" <eschwartz93@gmail.com>,
"René Scharfe" <l.s.r@web.de>,
"Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
"Michal Suchánek" <msuchanek@suse.de>,
"Raymond E . Pasco" <ray@ameretat.dev>,
demerphq <demerphq@gmail.com>, "Theodore Ts'o" <tytso@mit.edu>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [RFC PATCH 0/1] Canonical tar format for Git
Date: Sun, 5 Feb 2023 22:17:27 +0000 [thread overview]
Message-ID: <20230205221728.4179674-1-sandals@crustytoothpaste.net> (raw)
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 reply other threads:[~2023-02-05 22:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-05 22:17 brian m. carlson [this message]
2023-02-05 22:17 ` [RFC PATCH 1/1] Document a fixed tar format for interoperability brian m. carlson
2023-02-06 21:08 ` Junio C Hamano
2023-02-07 22:34 ` brian m. carlson
2023-02-06 22:18 ` Ævar Arnfjörð Bjarmason
2023-02-07 23:01 ` brian m. carlson
2023-02-08 11:07 ` Ævar Arnfjörð Bjarmason
2023-02-08 23:52 ` brian m. carlson
2023-02-09 0:35 ` Ævar Arnfjörð Bjarmason
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=20230205221728.4179674-1-sandals@crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=avarab@gmail.com \
--cc=demerphq@gmail.com \
--cc=eschwartz93@gmail.com \
--cc=git@vger.kernel.org \
--cc=konstantin@linuxfoundation.org \
--cc=l.s.r@web.de \
--cc=msuchanek@suse.de \
--cc=ray@ameretat.dev \
--cc=tytso@mit.edu \
/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).