From: Jeff King <peff@peff.net>
To: Reece Dunn <msclrhd@googlemail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [RFC] Line diff fragments, custom colour markers and word change highlighting
Date: Sat, 31 Jan 2009 01:57:42 -0500 [thread overview]
Message-ID: <20090131065742.GA3033@coredump.intra.peff.net> (raw)
In-Reply-To: <3f4fd2640901301244s34d94e0fka00ce2eb6f6bef48@mail.gmail.com>
On Fri, Jan 30, 2009 at 08:44:26PM +0000, Reece Dunn wrote:
> At the moment, I am manually editing the output of git diff to produce
> the desired output. I intend on modifying git to get it to produce the
> output in a format that I am interested in so that I don't have to
> edit it by hand.
Have you considered writing an external diff driver (see the description
of GIT_EXTERNAL_DIFF in git(1))? That would be a good starting point for
experimenting if you want to use a totally different diff driver (but if
you are just making tweaks to git's diff code, then obviously that isn't
a good idea).
Your RFCs look more like tweaks, but I wonder if there isn't already a
good external tool for doing these sorts of non-line-oriented diffs.
-Peff
prev parent reply other threads:[~2009-01-31 6:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-30 20:44 [RFC] Line diff fragments, custom colour markers and word change highlighting Reece Dunn
2009-01-31 6:57 ` Jeff King [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=20090131065742.GA3033@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=msclrhd@googlemail.com \
/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).