From: Junio C Hamano <gitster@pobox.com>
To: "João Victor Bonfim" <JoaoVictorBonfim@protonmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Fw: Curiosity
Date: Wed, 15 Dec 2021 10:07:20 -0800 [thread overview]
Message-ID: <xmqq8rwl91yf.fsf@gitster.g> (raw)
In-Reply-To: <wVwq9WVLpVt7MNLmIYOWCFKVSf8l532MD_vu4yTA8hl1fCARnW8nOUJjxYmKSzFw1SnPp5iYRD-aW4gAT2HnyQbC5aLBOvyT6npn88lxwNQ=@protonmail.com> ("João Victor Bonfim"'s message of "Wed, 15 Dec 2021 03:52:38 +0000")
João Victor Bonfim <JoaoVictorBonfim@protonmail.com> writes:
> I sent this message to Junio Hamano kinda of forever ago, since
> then I haven't been able to address it or do anything about it
> really...
My spam filter has learned that anything that goes to gitster@
address without cc'ed to the git@vger list are to be caught, so it
is very plausible that I didn't see it. Sending any inquiry here on
the list is the right thing to do, especially because it is likely
that I may not be the area expert for whatever you want to learn
about Git, while there are others who are more familiar with various
parts of the system and other ways the system is used.
You will also increase your chances to be read if you made your
message look more like the ones typically posted here (see the
archive), by wrapping overly long lines, etc.
> Since Git is almost used for everything at this point, is there
> any intent on providing better support for non textual file types?
> Why do I say this? Take this game mod which I follow as example ->
> https://github.com/SolariusScorch/XComFiles <- whenever I clone it
> Git takes a significant forever amount of time to download 452 MB
> of files whose some part, from my perspective, isn't being delta
> compressed like the text files are (since, whenever reading a log
> of what changes were made, git creates and undoes modes for all
> binary files, some of which only changed by a pixel from one
> colour to another).
Our delta compression does not care whether the contents are text or
binary, so if it is not compressed well, so it can be a sign that
the contents are not compressible to begin with, at least with the
xdelta binary-diff-patch engine we use. Improvement designs,
algorithms and patches are always welcome ;-)
next prev parent reply other threads:[~2021-12-15 18:07 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 [this message]
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
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=xmqq8rwl91yf.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=JoaoVictorBonfim@protonmail.com \
--cc=git@vger.kernel.org \
/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).