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

Re: [PATCH v2 2/2] send-email: handle adjacent RFC 2047-encoded words properly

From
Philip Oakley <philipoakley@iee.org>
Date
Dec 10, 2014, 21:51 UTC
Message-ID
<A6412B2B2F584CDC9ACCB22623CF789A@PhilipOakley>
In-Reply-To
<op.xqifqmyznngjn5@freezie>
From: "Роман Донченко" <dpb@corrigendum.ru>
Sent: Sunday, December 07, 2014 6:17 PM
Show 8 quoted lines
>> Would that be worth a terse comment in the documentation change part 
>> of  the patch?
>> "Multiple  (RFC2047) encodings are not supported.",
>> or would that be bike shed noise.
>
> I didn't change any documentation... and in either case, they weren't 
> supported in the first place, so I don't think it's anything I need to 
> mention.

I'd confused this with the crossing thread by Paolo Bonzini <bonzini@gnu.org> [PATCH 2/2] git-send-email: add --transfer-encoding option; 25 November 2014 14:00. $gmane/260217.

Sorry for the noise. -- Philip

Previous: Роман Донченко
Message 7 of 7 in “send-email: align RFC 2047 decoding more closely with the spec”
  1. 1/2 send-email: align RFC 2047 decoding more closely with the specРоман Донченко, Dec 6, 2014
  2. 2/2 send-email: handle adjacent RFC 2047-encoded words properlyРоман Донченко, Dec 6, 2014
  3. Jeff KingDec 7, 2014
  4. Роман ДонченкоDec 7, 2014
  5. Philip OakleyDec 7, 2014
  6. Роман ДонченкоDec 7, 2014
  7. Philip OakleyDec 10, 2014

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.