From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Paul Eggert <eggert@CS.UCLA.EDU>, git@vger.kernel.org
Subject: Re: [PATCH] Don't use $author_name undefined when $from contains no /\s</.
Date: Fri, 20 Oct 2006 09:21:51 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0610200911360.3962@g5.osdl.org> (raw)
In-Reply-To: <7vhcxzpgot.fsf@assigned-by-dhcp.cox.net>
On Fri, 20 Oct 2006, Junio C Hamano wrote:
>
> Coding a workaround is not a big deal; the change is simple and
> trivial.
Yeah, I sent Junio a patch that _should_ make git accept the patches
already, so technically it was easy.
What irritates me personally about the new format for "-u" is that
- Maybe "-u" is new as far as _POSIX_ is concerned, but daamn, it's been
a standard format for a hell of a long time in real life, and this was
a totally gratuitous change.
- The new format is very much a new "special case". Now a totally empty
line means exactly the same as a line that is " \n", so we have a new
special case that simply didn't use to exist - we used to be able to
just always skip the first character on a line, and consider the rest
of the line to be "the data". Now you can't do that any more.
The fact that GNU patch has always accepted total crap patches, has
always been a thorn in my side: GNU patch is simply too accepting by
default if you care about the integrity of the end result (I always ran
it with "-p1 --fuzz=0" just to at least fix the most egregious cases of
"we'll accept anything that loks even _remotely_ likely to apply")
- git-apply was being very strict with patches on purpose. The "empty
line in a patch" error has triggered several time for me, and at least
so far it has _not_ ever been due to a new GNU patch, but every time
due to a broken mailer or somebody not being careful when editing the
patch by hand. So triggering an error has been the _right_ thing to
do so far - it's been a big red sign saying "somebody did something bad
to this patch".
so I think the new format is strictly speaking a regression. It takes away
a good sanity-check, and we're stuck with having to handle old-style
patches _anyway_ for the forseeable future, so we can't replace it with a
new sanity check.
But it does seem like we have no choice, simply because people apparently
already use the broken version.
Linus
next prev parent reply other threads:[~2006-10-20 16:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-19 8:33 [PATCH] Don't use $author_name undefined when $from contains no /\s</ Jim Meyering
2006-10-19 16:19 ` Junio C Hamano
2006-10-19 18:16 ` Jim Meyering
2006-10-19 19:03 ` Junio C Hamano
2006-10-19 21:28 ` Paul Eggert
2006-10-19 21:34 ` Junio C Hamano
2006-10-19 23:48 ` Paul Eggert
2006-10-20 7:52 ` Junio C Hamano
2006-10-20 16:21 ` Linus Torvalds [this message]
2006-10-20 15:48 ` Jakub Narebski
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=Pine.LNX.4.64.0610200911360.3962@g5.osdl.org \
--to=torvalds@osdl.org \
--cc=eggert@CS.UCLA.EDU \
--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).