From: Junio C Hamano <gitster@pobox.com>
To: "João Victor Bonfim" <JoaoVictorBonfim@protonmail.com>
Cc: Martin Fick <mfick@codeaurora.org>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
git@vger.kernel.org
Subject: Re: Fw: Curiosity
Date: Fri, 17 Dec 2021 16:24:33 -0800 [thread overview]
Message-ID: <xmqq1r2a220u.fsf@gitster.g> (raw)
In-Reply-To: <1X3gQ48NK5aBDHcpYMlxESRjqubcCBKJUQu2K0dBOnTyvsXCXXoGDBg2Ff4KarK6WsZnzN3HgqHGOlCKKdF-wtZQ5tHsoAcfit2CTXMWqh4=@protonmail.com> ("João Victor Bonfim"'s message of "Sat, 18 Dec 2021 00:15:59 +0000")
João Victor Bonfim <JoaoVictorBonfim@protonmail.com> writes:
>> I suspect that for most algorithms and their implementations, this would
>>
>> not result in repeatable "recompressed" results. Thus the checked-out
>>
>> files might be different every time you checked them out. :(
>
> How or why?
>
> Sincere question.
Two immediate things that come to my mind are lossy compression
algorithms (jpeg pictures?) and compressors that do not necessarily
produce bit-for-bit identical results (e.g. gzip by default embeds
timestamp unless explicitly told not to from a command line option).
next prev parent reply other threads:[~2021-12-18 0:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Wlh_w2gSCDQ2ieJnIY7TStWrzxbwP98SNRIFMTYpva7SRFipqk63HEYFVF7wFn1oSHOkQNsjWGOa5L49vyRlvSLbuZqpmvOaDOHmFkdt2zw=@protonmail.com>
2021-12-15 3:52 ` Fw: Curiosity João Victor Bonfim
2021-12-15 18:07 ` Junio C Hamano
2021-12-15 23:45 ` João Victor Bonfim
2021-12-16 2:19 ` brian m. carlson
2021-12-16 21:20 ` João Victor Bonfim
2021-12-16 21:33 ` Martin Fick
2021-12-16 21:42 ` Junio C Hamano
2021-12-18 0:17 ` João Victor Bonfim
2021-12-18 0:15 ` João Victor Bonfim
2021-12-18 0:24 ` Junio C Hamano [this message]
2021-12-18 0:50 ` João Victor Bonfim
2021-12-18 1:06 ` Martin Fick
2021-12-18 1:34 ` brian m. carlson
2021-12-18 1:40 ` João Victor Bonfim
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=xmqq1r2a220u.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=JoaoVictorBonfim@protonmail.com \
--cc=git@vger.kernel.org \
--cc=mfick@codeaurora.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).