From: Paul Eggert <eggert@CS.UCLA.EDU>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Theodore Tso <tytso@mit.edu>,
Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Junio C Hamano <gitster@pobox.com>,
Andrew Morton <akpm@linux-foundation.org>,
Git Mailing List <git@vger.kernel.org>,
quilt-dev@nongnu.org
Subject: Re: being nice to patch(1)
Date: Tue, 03 Jul 2007 13:55:02 -0700 [thread overview]
Message-ID: <87zm2dxl5l.fsf@penguin.cs.ucla.edu> (raw)
In-Reply-To: <alpine.LFD.0.98.0707031159580.9434@woody.linux-foundation.org> (Linus Torvalds's message of "Tue, 3 Jul 2007 12:48:31 -0700 (PDT)")
Linus Torvalds <torvalds@linux-foundation.org> writes:
> Anyway, I tried to look at the patch sources, but I had to stop. That
> whole "intuit_diff_type()" function is probably designed as an initiation
> rite for any patch programmers, and to make sure that you have to be
> really serious about wanting to send patches before you can become part of
> the "in crowd". It's "mental hazing".
You should have seen it in the good old days when Larry Wall wrote it.
It was at least -- at least! -- 10% worse.
> In this case, the improvement would be to simply ignore indented patches
> (preferably by default, but at least have the option to do so).
I agree. POSIX has tied our hands to some extent, though, since it
_requires_ patch to accept indented patches by default. It's too late
to fix this in the current POSIX go-round, but we can fix it in the
next. And in the mean time we can add an option, I suppose defaulting
to not stripping indentation unless POSIXLY_CORRECT is set. That
would be fine with me.
I'll add it to my list of things to do.
next prev parent reply other threads:[~2007-07-03 21:10 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-02 19:54 being nice to patch(1) Andrew Morton
2007-07-02 21:16 ` Linus Torvalds
2007-07-02 21:25 ` Andrew Morton
2007-07-02 21:40 ` Linus Torvalds
2007-07-02 21:56 ` Andrew Morton
2007-07-03 0:28 ` Linus Torvalds
2007-07-03 4:00 ` Junio C Hamano
2007-07-03 4:14 ` Linus Torvalds
2007-07-03 12:04 ` Johannes Schindelin
2007-07-03 12:21 ` Paolo Ciarrocchi
2007-07-03 12:35 ` Johannes Schindelin
2007-07-03 18:39 ` Theodore Tso
2007-07-03 19:48 ` Linus Torvalds
2007-07-03 20:55 ` Paul Eggert [this message]
2007-07-03 21:30 ` Linus Torvalds
2007-07-03 21:35 ` Linus Torvalds
2007-07-03 13:22 ` David Kastrup
2007-07-03 13:39 ` Johannes Schindelin
2007-07-03 13:54 ` David Kastrup
2007-07-03 15:01 ` [PATCH] diff --no-index: fix --name-status with added files Johannes Schindelin
2007-07-03 15:01 ` being nice to patch(1) Johannes Schindelin
2007-07-03 15:08 ` David Kastrup
2007-07-06 12:38 ` David Kastrup
2007-07-06 15:22 ` git-diff memory/speed/disk impacts (was: being nice to patch(1)) David Kastrup
2007-07-06 18:08 ` being nice to patch(1) Linus Torvalds
2007-07-03 13:34 ` [Quilt-dev] " Andreas Gruenbacher
2007-07-03 15:49 ` Andrew Morton
2007-07-03 16:03 ` Linus Torvalds
2007-07-03 16:03 ` Andreas Gruenbacher
2007-07-03 16:15 ` Andrew Morton
2007-07-03 21:03 ` Andrew Morton
2007-07-03 21:03 ` Andrew Morton
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=87zm2dxl5l.fsf@penguin.cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=Johannes.Schindelin@gmx.de \
--cc=akpm@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paolo.ciarrocchi@gmail.com \
--cc=quilt-dev@nongnu.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/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).