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

Re: [PATCH] blame: Improve parsing for emails with spaces

From
JSJosh Stone <jistone@redhat.com>
Date
Apr 29, 2011, 18:17 UTC
Message-ID
<4DBB00CC.3030400@redhat.com>
In-Reply-To
<7vvcxxvsz4.fsf@alter.siamese.dyndns.org>
On 04/29/2011 10:59 AM, Junio C Hamano wrote:
> It would be an entirely different issue if the command barfed and refused
> to blame the file.

Yeah - the command doesn't fail outright. Anything that builds on blame/annotate would get bad data, but for me it's more of a formatting issue. In my actual bad commit, the author's "name <broken email" takes up 61 characters, making the whole blame output tediously wide.

Thanks for taking the patch.
Josh
Previous: Junio C HamanoNext: Jeff King
Message 5 of 6 in “blame: Improve parsing for emails with spaces”
  1. blame: Improve parsing for emails with spacesJosh Stone, Apr 21, 2011
  2. Jeff KingApr 29, 2011
  3. Junio C HamanoApr 29, 2011
  4. Junio C HamanoApr 29, 2011
  5. Josh StoneApr 29, 2011
  6. Jeff KingApr 29, 2011

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.