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

Re: git issue / [PATCH] MIPS: fix invalid symbolic link file

From
SWStephen Warren <swarren@wwwdotorg.org>
Date
Sep 19, 2013, 20:36 UTC
Message-ID
<523B605F.8090402@wwwdotorg.org>
In-Reply-To
<523B555E.2070508@kdbg.org>
On 09/19/2013 01:49 PM, Johannes Sixt wrote:
Show 9 quoted lines
> Am 19.09.2013 15:39, schrieb Ralf Baechle:
>> The original patch that introduced the symlink with the \n is kernel
>> commit 3b29aa5ba204c62b3ec8f9f5b1ebd6e5d74f75d3 and is archived in
>> patchwork at http://patchwork.linux-mips.org/patch/5745/  The patch
>> file contains a \n at the end - but one would expect that from a
>> patch file that has been transfered via email, so I'm not sure how this
>> is supposed to work with emailed patches?!?
> 
> The mbox file I downloaded from this link looks like this:
...
> but it should look like this:
...
> Whoever or whatever moved the '\ No newline at end of file' line above
> the patch text is to blame.

That sounds like a patchwork problem; the original copy of the message I received looks correct.

Previous: Johannes SixtNext: Junio C Hamano
Message 3 of 4 in “Re: git issue / [PATCH] MIPS: fix invalid symbolic link file”
  1. Ralf BaechleSep 19, 2013
  2. Johannes SixtSep 19, 2013
  3. Stephen WarrenSep 19, 2013
  4. Junio C HamanoSep 19, 2013

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.