From: Junio C Hamano <gitster@pobox.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
git@vger.kernel.org, "Emily Shaffer" <emilyshaffer@google.com>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>,
"Konstantin Ryabitsev" <konstantin@linuxfoundation.org>,
"Jason Pyeron" <jpyeron@pdinc.us>
Subject: Re: [PATCH 4/4] docs: note that archives are not stable
Date: Mon, 01 Mar 2021 10:15:29 -0800 [thread overview]
Message-ID: <xmqqpn0irb9a.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <YDvexO2NFM0KZ1Jo@camp.crustytoothpaste.net> (brian m. carlson's message of "Sun, 28 Feb 2021 18:19:48 +0000")
"brian m. carlson" <sandals@crustytoothpaste.net> writes:
> The output of 'git archive' is guaranteed to be the same across
> versions of git, but the archive itself is not guaranteed to be
> bit-for-bit identical.
I do not quite get this; your original was clearer. What does it
mean to "be the same across versions of git but not identical" at
the same time? If output from Git version 1.0 and 2.0 are guranteed
to be the same across versions, what more is there for the readers
to worry about the format stability?
Perhaps you meant
... is guaranteed to be the same for any given version of
Git across ports.
or something? It would allow kernel.org's use of "Konstantin tells
kernel.org users to use Git version X to run 'git archive' and
create detached signature on the output, and upload only the
signature. The site uses the same Git version X to run 'git
archive' to create a tarball and the detached signature magically
matches, as the output on two places are bit-for-bit identical".
> The output of 'git archive' has changed
> in the past, and most likely will in the future.
That is correct as a statement of fact. I feel that saying it is
either redundant and insufficient at the same time. If we want to
tell them "do not depend on the output being bit-for-bit identical",
we should say it more explicitly after this sentence, I would think.
next prev parent reply other threads:[~2021-03-01 18:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-27 19:18 [PATCH 0/4] Documentation updates to FAQ and git-archive brian m. carlson
2021-02-27 19:18 ` [PATCH 1/4] docs: add a question on syncing repositories to the FAQ brian m. carlson
2021-02-28 13:01 ` Ævar Arnfjörð Bjarmason
2021-03-15 20:40 ` brian m. carlson
2021-02-27 19:18 ` [PATCH 2/4] docs: add line ending configuration article to FAQ brian m. carlson
2021-02-27 19:18 ` [PATCH 3/4] docs: add a FAQ section on push and fetch problems brian m. carlson
2021-02-28 12:37 ` Ævar Arnfjörð Bjarmason
2021-02-28 18:07 ` brian m. carlson
2021-03-01 18:02 ` Junio C Hamano
2021-02-27 19:18 ` [PATCH 4/4] docs: note that archives are not stable brian m. carlson
2021-02-28 12:48 ` Ævar Arnfjörð Bjarmason
2021-02-28 18:19 ` brian m. carlson
2021-02-28 18:46 ` Ævar Arnfjörð Bjarmason
2021-03-01 18:15 ` Junio C Hamano [this message]
2021-03-03 0:36 ` brian m. carlson
2021-03-03 6:55 ` Junio C Hamano
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=xmqqpn0irb9a.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=jpyeron@pdinc.us \
--cc=konstantin@linuxfoundation.org \
--cc=sandals@crustytoothpaste.net \
/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).