From: "Soni L." <fakedme+git@gmail.com>
To: Stefan Beller <sbeller@google.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Delta compression hooks
Date: Thu, 4 May 2017 20:40:22 -0300 [thread overview]
Message-ID: <6e5b70c3-cf80-d26a-1c7e-14c2a00a778b@gmail.com> (raw)
In-Reply-To: <CAGZ79ka66czcGpNGWFEQ=2Qf7OJgH7A-O+R860P=usiFWV4RBA@mail.gmail.com>
On 2017-05-04 07:57 PM, Stefan Beller wrote:
> On Thu, May 4, 2017 at 3:48 PM, Soni L. <fakedme+git@gmail.com> wrote:
>> Can we get delta compression hooks? I'm working with voxel data as my source
>> code (it's a long story...) and git doesn't handle changing lines of voxels
>> very well.
>>
>> Example, I have something from position (0,0,0) to position (0,10,0) and I
>> replace it with something else. Git doesn't handle this difference very well
>> if the file is encoded in XYZ order (it'd handle it exceptionally well if
>> the file was in YXZ or YZX order), and Z-order curves aren't much better.
>> It's even worse if the file is compressed.
> Maybe look into smudge filters to store the data in a different format
> inside Git
> than what is in the working tree.
>
> https://git-scm.com/docs/gitattributes
Those can only do so much. The best it can do is re-encode voxel data
into Z-order curves, or recompress files into pseudo-compressed format
(valid gzip file but every block is of type "uncompressed data").
I want something that can say "this file is 3D and we change a line of
voxels here".
prev parent reply other threads:[~2017-05-04 23:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-04 22:48 Delta compression hooks Soni L.
2017-05-04 22:57 ` Stefan Beller
2017-05-04 23:40 ` Soni L. [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6e5b70c3-cf80-d26a-1c7e-14c2a00a778b@gmail.com \
--to=fakedme+git@gmail.com \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).