From: matthew@giassa.net
To: git@vger.kernel.org
Subject: Question: xdiff and "pretty" (human readable) diff output
Date: Wed, 22 Mar 2017 12:23:40 -0700 [thread overview]
Message-ID: <20170322192340.elg2gpvcshhk3jq3@darkstar> (raw)
Good day,
I have a question with respect to how git generates "pretty" (ie: human
readable) unified diffs. It's to my understanding that git uses its own
(simplified/minimized) fork of libxdiff, simply referred to as "xdiff"
[1]. Which tool/library is used to take the xdiff output and generate
the human-readable equivalent that is rendered to the console? I have a
program that I'm maintaining that currently tracks changes to a couple
of "sandboxed" files, and I wanted to add a simple console UI that
periodically shows the changes to the files over time and/or dumps the
"pretty diff" to syslog.
Thank you.
1. "Use a *real* built-in diff generator · git/git@3443546",
<https://github.com/git/git/commit/3443546f6ef57fe28ea5cca232df8e400bfc3883>,
Accessed 2017-03-22
--Matthew
next reply other threads:[~2017-03-22 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-22 19:23 matthew [this message]
2017-03-22 19:43 ` Question: xdiff and "pretty" (human readable) diff output Stefan Beller
2017-03-22 19:47 ` matthew
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=20170322192340.elg2gpvcshhk3jq3@darkstar \
--to=matthew@giassa.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox