From: A Large Angry SCM <gitzilla@gmail.com>
To: Robert Fitzsimons <robfitz@273k.net>
Cc: Linus Torvalds <torvalds@osdl.org>, git@vger.kernel.org
Subject: Re: [PATCH 6/9] New option --ignore-whitespace for git-apply.
Date: Sun, 28 Aug 2005 16:49:35 -0400 [thread overview]
Message-ID: <4312235F.2040907@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0508280956320.3317@g5.osdl.org>
Linus Torvalds wrote:
> On Sun, 28 Aug 2005, Robert Fitzsimons wrote:
>>Allow the user to force a patch to be applied even though there might
>>be whitespace differences. Added a test case for the new option.
>
> If you ignore whitespace, then you should probably accept patches that are
> whitespace corrupted in another way: lines missing the ' ' at the
> beginning. Especially lines that are empty. That's actually the most
> common form of whitespace corruption there is.
Actually, a more restricted from of --ignore-whitespace may be useful,
--ignore-trailing-whitespace (needs a shorter name!). Ignore only
trailing whitespace differences (including empty context lines without
the initial space).
next prev parent reply other threads:[~2005-08-28 20:49 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-28 15:24 [PATCH 1/9] Fix git patch header processing in git-apply Robert Fitzsimons
2005-08-28 15:24 ` [PATCH 2/9] Fix detection of files with only one line " Robert Fitzsimons
2005-08-28 15:24 ` [PATCH 3/9] Fix processing of a patch file which modifies the same file " Robert Fitzsimons
2005-08-28 15:24 ` [PATCH 4/9] Fix the procssing of multiple patch files with --check " Robert Fitzsimons
2005-08-28 15:24 ` [PATCH 5/9] New option --force-delete for git-apply Robert Fitzsimons
2005-08-28 15:24 ` [PATCH 6/9] New option --ignore-whitespace " Robert Fitzsimons
2005-08-28 15:24 ` [PATCH 7/9] New option --ignore-applied " Robert Fitzsimons
2005-08-28 15:25 ` [PATCH 8/9] New git-apply test cases for patches with mulitple fragments Robert Fitzsimons
2005-08-28 15:25 ` [PATCH 9/9] New git-apply test cases for scanning forwards and backwards Robert Fitzsimons
2005-08-28 16:58 ` [PATCH 6/9] New option --ignore-whitespace for git-apply Linus Torvalds
2005-08-28 20:49 ` A Large Angry SCM [this message]
2005-08-28 21:06 ` Junio C Hamano
2005-08-28 21:06 ` [PATCH 5/9] New option --force-delete " Junio C Hamano
2005-08-28 21:06 ` [PATCH 3/9] Fix processing of a patch file which modifies the same file in git-apply Junio C Hamano
2005-08-28 16:55 ` [PATCH 2/9] Fix detection of files with only one line " Linus Torvalds
2005-08-28 23:39 ` [PATCH 1/9] Fix git patch header processing " Junio C Hamano
2005-08-29 23:58 ` Robert Fitzsimons
2005-08-30 0:47 ` Linus Torvalds
2005-08-30 1:09 ` Junio C Hamano
2005-08-30 1:24 ` Linus Torvalds
2005-08-30 1:34 ` Junio C Hamano
2005-08-30 2:00 ` Linus Torvalds
2005-08-30 7:36 ` Martin Langhoff
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=4312235F.2040907@gmail.com \
--to=gitzilla@gmail.com \
--cc=git@vger.kernel.org \
--cc=robfitz@273k.net \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).