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

Re: [BUG] format-patch does not wrap From-field after author name

From
Jeff King <peff@peff.net>
Date
Apr 15, 2011, 03:30 UTC
Message-ID
<20110415033003.GB19621@sigill.intra.peff.net>
In-Reply-To
<BANLkTim0Q+RaExss+U3m-=CHT6Jd1jc56Q@mail.gmail.com>
On Fri, Apr 15, 2011 at 12:43:08AM +0200, Erik Faye-Lund wrote:
Show 24 quoted lines
> >> That part is surprisingly easy: If it contains a '<', then it's on the form
> >> "Foo Bar Baz <foo@bar.baz>". If not, it's "foo@bar.baz" (assuming it's
> >> UTF-8 encoded rfc5322 mailbox'es we assume, which would make the most
> >> sense to me)
> >
> > What about:
> >
> >  "Foo \"The Bar\" Baz" <foo@example.com>
> >
> > or
> >
> >  Foo "The Bar" Baz <foo@example.com>
> >
> > or
> >
> >  Foo (The Bar) Baz <foo@example.com>
> >
> > I.e., are we taking rfc822-style addresses, or are we taking something
> > that looks vaguely like an email address, and just treating everything
> > left of "<" as literal?
> 
> I was just thinking of interpreting everything left of '<' literally
> and encode it (if needed). Currently, we interpret the entire string
> literally, encoding the name would an improvement.

Won't that be a regression for people who already know that we take things literally and are manually quoting and/or rfc2047-encoding the contents?

-Peff
Previous: Erik Faye-LundNext: Erik Faye-Lund
Message 10 of 15 in “[BUG] format-patch does not wrap From-field after author name”
  1. Erik Faye-LundApr 14, 2011
  2. Junio C HamanoApr 14, 2011
  3. Jeff KingApr 14, 2011
  4. Erik Faye-LundApr 14, 2011
  5. Jeff KingApr 14, 2011
  6. Jeff KingApr 14, 2011
  7. Erik Faye-LundApr 14, 2011
  8. Jeff KingApr 14, 2011
  9. Erik Faye-LundApr 14, 2011
  10. Jeff KingApr 15, 2011
  11. Erik Faye-LundApr 15, 2011
  12. Jeff KingApr 16, 2011
  13. Jeff KingApr 14, 2011
  14. Erik Faye-LundApr 14, 2011
  15. Erik Faye-LundApr 14, 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.