From: Nikolaus Rath <Nikolaus@rath.org>
To: David Lang <david@lang.hm>
Cc: git@vger.kernel.org
Subject: Re: Working with zip files
Date: Tue, 16 Aug 2016 09:32:47 -0700 [thread overview]
Message-ID: <87shu4wu6o.fsf@thinkpad.rath.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1608160926330.11774@nftneq.ynat.uz> (David Lang's message of "Tue, 16 Aug 2016 09:27:55 -0700 (PDT)")
On Aug 16 2016, David Lang <david@lang.hm> wrote:
> On Tue, 16 Aug 2016, Nikolaus Rath wrote:
>
>> I would like to store Simulink models in a Git
>> repository. Unfortunately, the file format is binary. But luckily, the
>> binary format happens to be a zipfile containing nicely formatted XML
>> files.
>>
>> Is there a way to teach Git to take advantage of this when storing,
>> diff-ing and merging these files?
>
> you should be able to use clean/smudge to have git store the files
> uncompressed, which will help a lot.
Cool, I'll look into that.
> I think there's a way to tell it to do a xml aware diff/patch, but I
> don't remember how.
Oh, I didn't even want to go that far. I'm perfectly happy if it does a
text-based diff/patch of the contained XML files. Would clean/smudge
provide that already?
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
next prev parent reply other threads:[~2016-08-16 16:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 16:25 Working with zip files Nikolaus Rath
2016-08-16 16:27 ` David Lang
2016-08-16 16:32 ` Nikolaus Rath [this message]
2016-08-16 16:48 ` David Lang
2016-08-16 16:58 ` Junio C Hamano
2016-08-16 19:56 ` Jakub Narębski
2016-08-16 20:19 ` Junio C Hamano
2016-08-18 12:16 ` Jakub Narębski
2016-08-18 16:56 ` David Lang
2016-08-18 17:45 ` Jakub Narębski
2016-08-19 3:00 ` David Lang
2016-08-16 21:14 ` Nikolaus Rath
2016-08-17 5:31 ` Jacob Keller
2016-08-17 9:58 ` David Lang
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=87shu4wu6o.fsf@thinkpad.rath.org \
--to=nikolaus@rath.org \
--cc=david@lang.hm \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.