From: Jonathan Lebon <jonathan.lebon@gmail.com>
To: git@vger.kernel.org
Cc: peff@peff.net, Jonathan Lebon <jonathan.lebon@gmail.com>
Subject: [PATCH 0/4] diff-highlight: make a few improvements
Date: Mon, 2 Nov 2015 21:05:30 -0500 [thread overview]
Message-ID: <1446516334-27652-1-git-send-email-jonathan.lebon@gmail.com> (raw)
These patches bring a few improvements to the contrib/diff-highlight
Perl script. The major improvement is done in patch 3/4, which improves
diff-highlighting accuracy by implementing a recursive line matching
algorithm.
Please note that I have limited experience with Perl, so there may be
better ways to do things. (Let me know if that is the case!)
Jonathan Lebon (4):
diff-highlight: add `less -r` to cmd in README
diff-highlight: factor out prefix/suffix functions
diff-highlight: match up lines before highlighting
diff-highlight: add maxhunksize config option
contrib/diff-highlight/README | 87 +++++-----------
contrib/diff-highlight/diff-highlight | 189 ++++++++++++++++++++++++----------
2 files changed, 161 insertions(+), 115 deletions(-)
--
2.6.0
next reply other threads:[~2015-11-03 2:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 2:05 Jonathan Lebon [this message]
2015-11-03 2:05 ` [PATCH 1/4] diff-highlight: add `less -r` to cmd in README Jonathan Lebon
2015-11-03 2:41 ` Junio C Hamano
2015-11-03 3:12 ` Jonathan Lebon
2015-11-03 21:14 ` Jeff King
2015-11-03 21:51 ` Junio C Hamano
2015-11-03 21:55 ` Jeff King
2015-11-03 2:05 ` [PATCH 2/4] diff-highlight: factor out prefix/suffix functions Jonathan Lebon
2015-11-03 21:17 ` Jeff King
2015-11-03 2:05 ` [PATCH 3/4] diff-highlight: match up lines before highlighting Jonathan Lebon
2015-11-03 21:44 ` Jeff King
2015-11-03 22:03 ` Jeff King
2015-11-17 5:18 ` Jonathan Lebon
2015-11-17 22:50 ` Jeff King
2015-11-03 2:05 ` [PATCH 4/4] diff-highlight: add maxhunksize config option Jonathan Lebon
2015-11-03 21:46 ` Jeff King
2015-11-03 22:07 ` [PATCH 0/4] diff-highlight: make a few improvements Jeff King
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=1446516334-27652-1-git-send-email-jonathan.lebon@gmail.com \
--to=jonathan.lebon@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.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).