From: "Philip Oakley" <philipoakley@iee.org>
To: "Роман Донченко" <dpb@corrigendum.ru>
Cc: git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Jay Soffian" <jaysoffian@gmail.com>,
"Thomas Rast" <tr@thomasrast.ch>, "Jeff King" <peff@peff.net>
Subject: Re: [PATCH v2 2/2] send-email: handle adjacent RFC 2047-encoded words properly
Date: Wed, 10 Dec 2014 22:21:10 -0000 [thread overview]
Message-ID: <A6412B2B2F584CDC9ACCB22623CF789A@PhilipOakley> (raw)
In-Reply-To: op.xqifqmyznngjn5@freezie
From: "Роман Донченко" <dpb@corrigendum.ru>
Sent: Sunday, December 07, 2014 6:17 PM
>> 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
next prev parent reply other threads:[~2014-12-10 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-06 19:36 [PATCH v2 1/2] send-email: align RFC 2047 decoding more closely with the spec Роман Донченко
2014-12-06 19:36 ` [PATCH v2 2/2] send-email: handle adjacent RFC 2047-encoded words properly Роман Донченко
2014-12-07 9:18 ` Jeff King
2014-12-07 14:35 ` Роман Донченко
2014-12-07 17:48 ` Philip Oakley
2014-12-07 18:17 ` Роман Донченко
2014-12-10 22:21 ` Philip Oakley [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-12-14 15:59 [PATCH v2 1/2] send-email: align RFC 2047 decoding more closely with the spec Роман Донченко
2014-12-14 15:59 ` [PATCH v2 2/2] send-email: handle adjacent RFC 2047-encoded words properly Роман Донченко
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=A6412B2B2F584CDC9ACCB22623CF789A@PhilipOakley \
--to=philipoakley@iee.org \
--cc=avarab@gmail.com \
--cc=dpb@corrigendum.ru \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@gmail.com \
--cc=peff@peff.net \
--cc=tr@thomasrast.ch \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).