git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Martin Langhoff <martin@catalyst.net.nz>
Cc: git@vger.kernel.org, jmacd@cs.berkeley.edu
Subject: Re: [offtopic?] xdelta patch format wrapper
Date: Tue, 12 Feb 2008 19:56:53 -0800	[thread overview]
Message-ID: <7vprv1y0e2.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <47B26830.6090501@catalyst.net.nz> (Martin Langhoff's message of "Wed, 13 Feb 2008 16:46:56 +1300")

Martin Langhoff <martin@catalyst.net.nz> writes:

> Junio C Hamano wrote:
>> I am lost as to your objective because you seem to be keeping a
>> whole LOT more than I would have imagined for a specialized
>> purpose file format.
>
> My source files are 2 zipfiles that I know contain 1 xml file, and then
> may contain any arbitrary files. As a specialised file format is a
> pretty general case ;-) Because of compression, xdeltas of the zipfiles
> aren't good. So what I want to do is to diff the 2 unzipped directories
> - nothing git-specific, I could use diff -urN.
>
> Git diff *is* better in that it handles binary files, but we pay a
> sizable cost in being reversible.

Did I forget to say that I am Ok with --oneway option?

In fact, we started as oneway but we _fixed_ it to make it
reversible soon after the initial version ;-)  So "git apply"
still can grok oneway format.

  reply	other threads:[~2008-02-13  3:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-13  1:53 [offtopic?] xdelta patch format wrapper Martin Langhoff
2008-02-13  3:32 ` Junio C Hamano
2008-02-13  3:46   ` Martin Langhoff
2008-02-13  3:56     ` Junio C Hamano [this message]
2008-02-13 11:33     ` Johannes Schindelin
2008-02-13 17:53       ` Martin Langhoff
2008-02-13  4:13   ` Martin Langhoff

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=7vprv1y0e2.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jmacd@cs.berkeley.edu \
    --cc=martin@catalyst.net.nz \
    /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).