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

Re: a bug about format-patch of multibyte characters comment

From
Xxiaozhu <xiaozhu@gmail.com>
Date
Feb 13, 2011, 10:50 UTC
Message-ID
<4D57B76B.6000600@gmail.com>
In-Reply-To
<20110213102627.GB7735@sigill.intra.peff.net>
> Ah, OK, our mails just crossed paths. git-am already parses this
> correctly (actually, it is git-mailinfo that parses on behalf of
> git-am). We just need format-patch to generate it (and it should also
> probably be folding long lines in general).

I tested it, yes, the git-am parses it "correctly". There is only one problem that we lost the line break after import a patch. Is there a way that we can retain the line break after import the patch?

-xzer
Previous: Jeff KingNext: Jeff King
Message 10 of 13 in “a bug about format-patch of multibyte characters comment”
  1. xiaozhuFeb 12, 2011
  2. Martin KrügerFeb 12, 2011
  3. Jeff KingFeb 13, 2011
  4. Jeff KingFeb 13, 2011
  5. xiaozhuFeb 13, 2011
  6. Jeff KingFeb 13, 2011
  7. xiaozhuFeb 13, 2011
  8. xzerFeb 13, 2011
  9. Jeff KingFeb 13, 2011
  10. xiaozhuFeb 13, 2011
  11. Jeff KingFeb 13, 2011
  12. Johannes SixtFeb 13, 2011
  13. Jeff KingFeb 13, 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.