From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Paul Mackerras" <paulus@samba.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [RFD] Strange patch formats (aka tricks with unified diffs)..
Date: Fri, 13 Apr 2007 19:01:14 +1200 [thread overview]
Message-ID: <46a038f90704130001u4161f309k7bb98bb4801ef04a@mail.gmail.com> (raw)
In-Reply-To: <7v3b34hjdh.fsf@assigned-by-dhcp.cox.net>
On 4/13/07, Junio C Hamano <junkio@cox.net> wrote:
> "Martin Langhoff" <martin.langhoff@gmail.com> writes:
>
> > On 4/13/07, Paul Mackerras <paulus@samba.org> wrote:
> >> Side-by-side would be more challenging.
> >
> > <wish>If someone gets started on side-by-side, I'd love to have
> > char-level diff colouring,...
> > icecream too.</wish>
>
> Is it different from the --color-words (whose implementation I
> happen to hate)?
Didn't know about --color-words (goes away, tests...) no, nothing like
that. I don't like --color-words.
To see what I mean, try
git-show v1.4.4:git-cvsserver.perl > file1
git-show v1.5.1:git-cvsserver.perl > file2
xxdiff file1 file2
Just press 'n' twice to get to the 2nd "hunk" and you'll see what I
mean. Next is 'n', previous is 'p'. It's useful to visualise subtle
differences, and to spot commonalities in large changes.
Some aspects of xxdiff UI are horrid but this feature... is great.
Probably tries a scan for commonalities from the start and end of the
line. And then perhaps from the middle or from each beginning of alpha
char sequence.
cheers,
m
next prev parent reply other threads:[~2007-04-13 7:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 21:58 [RFD] Strange patch formats (aka tricks with unified diffs) Linus Torvalds
2007-04-12 23:02 ` Junio C Hamano
2007-04-13 5:38 ` Marco Costalba
2007-04-17 18:02 ` Marco Costalba
2007-04-13 5:43 ` Paul Mackerras
2007-04-13 6:07 ` Martin Langhoff
2007-04-13 6:35 ` Junio C Hamano
2007-04-13 7:01 ` Martin Langhoff [this message]
2007-04-14 8:59 ` Johannes Schindelin
2007-04-14 9:55 ` Junio C Hamano
2007-04-14 10:09 ` Jeff King
2007-04-13 15:16 ` Linus Torvalds
2007-04-18 1:44 ` Paul Mackerras
2007-04-18 4:02 ` Linus Torvalds
2007-04-13 8:10 ` Matthias Lederhofer
2007-04-13 15:00 ` Linus Torvalds
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=46a038f90704130001u4161f309k7bb98bb4801ef04a@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=paulus@samba.org \
--cc=torvalds@linux-foundation.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