git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Question: libxdiff: text-patches: internal format
@ 2017-03-23 18:00 matthew
  2017-03-23 19:30 ` René Scharfe
  0 siblings, 1 reply; 2+ messages in thread
From: matthew @ 2017-03-23 18:00 UTC (permalink / raw)
  To: git

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.

Thank you.

-- 
Matthew Giassa
e: matthew@giassa.net


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-03-23 19:30 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-03-23 18:00 Question: libxdiff: text-patches: internal format matthew
2017-03-23 19:30 ` René Scharfe

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).