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

Re: missing handling of "No newline at end of file" in git am

From
EWEric Wong <e@80x24.org>
Date
Feb 20, 2017, 08:06 UTC
Message-ID
<20170220080639.GA3802@starla>
In-Reply-To
<20170215114430.GD16249@aepfle.de>
Olaf Hering <olaf@aepfle.de> wrote:
Show 6 quoted lines
> On Tue, Feb 14, Olaf Hering wrote:
> 
> > How would I debug it?
> 
> One line is supposed to be longer than 998 chars, but something along
> the way truncated it and corrupted the patch.
998 sounds like the SMTP limit.

Perhaps git format-patch should emit binary diffs in that case? I doubt any human would bother reading excessively long lines as text...

Previous: Olaf HeringNext: Jeff King
Message 5 of 6 in “missing handling of "No newline at end of file" in git am”
  1. Olaf HeringFeb 14, 2017
  2. Junio C HamanoFeb 14, 2017
  3. Olaf HeringFeb 14, 2017
  4. Olaf HeringFeb 15, 2017
  5. Eric WongFeb 20, 2017
  6. Jeff KingFeb 14, 2017

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.