From: Timur Tabi <timur@freescale.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] teach diff machinery about --ignore-space-at-eol
Date: Wed, 14 Feb 2007 11:18:15 -0600 [thread overview]
Message-ID: <45D34457.8050207@freescale.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0702140125410.22628@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
> `git diff --ignore-space-at-eol` will ignore whitespace at the
> line ends.
>
> Signed-off-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>
This patch works great! Oh git maintainer, please please please please apply
this patch to the next version of git. My descendants will sing praises to your
glory for a thousand years.
--
Timur Tabi
Linux Kernel Developer @ Freescale
prev parent reply other threads:[~2007-02-14 17:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 21:59 How do I get git-format-patch to ignore changes that remove spaces from the end of the line? Timur Tabi
2007-02-13 22:24 ` Junio C Hamano
2007-02-13 22:36 ` Timur Tabi
2007-02-14 0:30 ` [PATCH] teach diff machinery about --ignore-space-at-eol Johannes Schindelin
2007-02-14 5:28 ` Timur Tabi
2007-02-14 17:18 ` Timur Tabi [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=45D34457.8050207@freescale.com \
--to=timur@freescale.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).