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

Re: [PATCH RFC] mailinfo: correctly handle multiline 'Subject:' header

From
APAlexander Potashev <aspotashev@gmail.com>
Date
Jan 8, 2009, 10:08 UTC
Message-ID
<20090108100813.GA15640@myhost>
In-Reply-To
<1230316721-14339-1-git-send-email-kirr@mns.spb.ru>
On 21:38 Fri 26 Dec     , Kirill Smelkov wrote:
Show 8 quoted lines
> When native language (RU) is in use, subject header usually contains several
> parts, e.g.
> 
> Subject: [Navy-patches] [PATCH]
> 	=?utf-8?b?0JjQt9C80LXQvdGR0L0g0YHQv9C40YHQvtC6INC/0LA=?=
> 	=?utf-8?b?0LrQtdGC0L7QsiDQvdC10L7QsdGF0L7QtNC40LzRi9GFINC00LvRjyA=?=
> 	=?utf-8?b?0YHQsdC+0YDQutC4?=
> 
Show 5 quoted lines
>  t/t5100/info0012    |    5 ++++
>  t/t5100/msg0012     |    7 ++++++
>  t/t5100/patch0012   |   30 +++++++++++++++++++++++++++++
>  t/t5100/sample.mbox |   52 +++++++++++++++++++++++++++++++++++++++++++++++++++
>  6 files changed, 112 insertions(+), 2 deletions(-)

The testcases are too long, a minimal mbox with encoded "Subject:" would be enough to test the mailinfo parser, it's all the you need to test here.

Previous: Junio C HamanoNext: Kirill Smelkov
Message 5 of 12 in “mailinfo: correctly handle multiline 'Subject:' header”
  1. mailinfo: correctly handle multiline 'Subject:' headerKirill Smelkov, Dec 26, 2008
  2. Kirill SmelkovJan 7, 2009
  3. Junio C HamanoJan 8, 2009
  4. Junio C HamanoJan 8, 2009
  5. Alexander PotashevJan 8, 2009
  6. Kirill SmelkovJan 8, 2009
  7. Kirill SmelkovJan 10, 2009
  8. Junio C HamanoJan 11, 2009
  9. Kirill SmelkovJan 12, 2009
  10. Junio C HamanoJan 12, 2009
  11. Kirill SmelkovJan 13, 2009
  12. Kirill SmelkovJan 14, 2009

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.