git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Fw: [PATCH] Documentation: networking: device drivers: Remove stray asterisks

From
Linus Torvalds <torvalds@linux-foundation.org>
Date
Dec 1, 2019, 01:20 UTC
Message-ID
<CAHk-=wj8tNhu76yxShwOfwVKk=qWznSFkAKyQfu6adcV8JzJkQ@mail.gmail.com>
In-Reply-To
<20191130180301.5c39d8a4@lwn.net>
On Sat, Nov 30, 2019 at 5:03 PM Jonathan Corbet <corbet@lwn.net> wrote:
>
> Attached.  The patch itself was not an attachment, but it was
> base64-encoded.

Ok, so presumably git removed the CRLF from the email, but then the base64 encoded part had another set of CRLF.

And when I try to apply that patch (in a test-tree reset to commit facd86390be2, so I think the patch should apply) I see the CRLF in .git/rebase-apply/patch, but then I get

  error: patch failed: Documentation/networking/device_drivers/intel/e100.rst:1
  error: Documentation/networking/device_drivers/intel/e100.rst: patch
does not apply
for every hunk. I assume that's because the CR part doesn't match the old code.

But my git version is d9f6f3b619 ("The first batch post 2.24 cycle") and some private patches.

So the problem might be limited to only some versions. I'm surprised, though - when git applies patches, it really wants the surrounding lines to match exactly. The extra CR at the end of the lines should have made that test fail.

Do you use some special options for git? Like --whitespace=nowarn or --3way or something like that?

            Linus
Previous: Jonathan CorbetNext: Jonathan Corbet
Message 2 of 8 in “Fw: [PATCH] Documentation: networking: device drivers: Remove stray asterisks”
  1. Jonathan CorbetDec 1, 2019
  2. Linus TorvaldsDec 1, 2019
  3. Jonathan CorbetDec 1, 2019
  4. Junio C HamanoDec 1, 2019
  5. Linus TorvaldsDec 1, 2019
  6. Junio C HamanoDec 1, 2019
  7. Amit ChoudharyDec 2, 2019
  8. Junio C HamanoDec 2, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.