git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Scharfe" <l.s.r@web.de>
To: matthew@giassa.net
Cc: git@vger.kernel.org
Subject: Re: Question: libxdiff: text-patches: internal format
Date: Thu, 23 Mar 2017 20:30:41 +0100	[thread overview]
Message-ID: <e19893df-0f7c-cfa7-cca4-014630ccf908@web.de> (raw)
In-Reply-To: <20170323180026.7qdfdzqgyczt2s3f@darkstar>

Am 23.03.2017 um 19:00 schrieb matthew@giassa.net:
> Hi there,
>
> Following up on an earlier question of mine from yesterday, is there any
> formal documentation (save for source diving) on the internal format
> used by libxdiff/xdiff when it generates a patch by comparing two
> plaintext files?
>
> I'd like to generate a human-readable "pretty" diff from the output
> generated by libxdiff, and while the suggestion by Stefan yesterday is a
> good idea (ie: go through diff.c), I'm trying to see if there's a
> quicker way to pull this off. Also, I can't determine if lifting that
> code from git would invoke LGPL licensing constraints (no problem), or
> GPL licensing constraints (incompatible with my application). If the
> format is easy enough to follow, I might just write my own parser,
> provided it's a trivial task.

Some of your questions may be answered on the homepage of LibXDiff, 
http://www.xmailserver.org/xdiff-lib.html.  That's the original version 
that was imported into Git long ago.  It lacks some Git-specific 
features, but the documentation and links on the web page may still help 
you.  The original LibXDiff is licensed under the LGPL and perhaps you 
can use it directly already.

René

      reply	other threads:[~2017-03-23 19:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 18:00 Question: libxdiff: text-patches: internal format matthew
2017-03-23 19:30 ` René Scharfe [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e19893df-0f7c-cfa7-cca4-014630ccf908@web.de \
    --to=l.s.r@web.de \
    --cc=git@vger.kernel.org \
    --cc=matthew@giassa.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).