Re: [PATCH/RFC] git-am: Make it easier to see which patch failed
- From
Jeff King <peff@peff.net>
- Date
- Jan 18, 2009, 17:07 UTC
- Message-ID
- <20090118170711.GA17055@coredump.intra.peff.net>
- In-Reply-To
- <alpine.DEB.1.00.0901181711090.3586@pacific.mpi-cbg.de>
On Sun, Jan 18, 2009 at 05:17:43PM +0100, Johannes Schindelin wrote:
Show 7 quoted lines
> > Yes, I'm surprised Junio doesn't remember the mass conversions we > > already had to do (4b7cc26a and 293623ed). But looking at the date, I > > guess it _has_ been a year and a half. :) > > Hey, be nice to Junio. Have you seen the amount of mails on this list > recently? I think Junio's the only one really reading all of them; even > if you were right, he would be entitled to a nicer reminder.
I didn't mean to be mean. On the contrary, I was surprised because _he_ usually is the one reminding _me_ about such fixes. I guess Junio is human, after all. :)
> But you are wrong. And Stephan is wrong, too. > > The name "FIRSTLINE" suggests that it is indeed a first line, and > consequently cannot contain a newline.
It is not "this is a problem because it might contain a newline" but "this is a problem because it might contain an escape sequence, _an example_ of which is a \n newline." So the question is whether you can guarantee that $FIRSTLINE does not contain a backslash. Which I don't think is the case here.
-Peff