From: Jeff King <peff@peff.net>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: git@vger.kernel.org
Subject: Re: Why a _full_ diff? (was: [PATCH] Char: serial167, cleanup (fwd))
Date: Mon, 12 Feb 2007 03:51:03 -0500 [thread overview]
Message-ID: <20070212085102.GA12605@coredump.intra.peff.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0702120934120.10436@chinchilla.sonytel.be>
On Mon, Feb 12, 2007 at 09:39:46AM +0100, Geert Uytterhoeven wrote:
> At first I thought the new version had CR/LF line endings or so, but that
> isn't the case.
Close. It looks like tabs/spaces changes. Try
git show 44bafd | cat -A | less
-Peff
next prev parent reply other threads:[~2007-02-12 8:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 8:39 Why a _full_ diff? (was: [PATCH] Char: serial167, cleanup (fwd)) Geert Uytterhoeven
2007-02-12 8:51 ` Jeff King [this message]
2007-02-12 9:20 ` Jeff King
2007-02-12 9:38 ` Jeff King
2007-02-12 12:00 ` Johannes Schindelin
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=20070212085102.GA12605@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=geert@linux-m68k.org \
--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