From: Christian Ludwig <chrissicool@gmail.com>
To: git@vger.kernel.org
Subject: git-send-email: Support for Reply-To
Date: Sun, 4 Mar 2018 00:58:12 +0100 [thread overview]
Message-ID: <20180303235814.7241-1-chrissicool@gmail.com> (raw)
Hi,
this is the third iteration of this series. There was a request to
rebase the changes on the refactoring patch b6049542 ("send-email:
extract email-parsing code into a subroutine", 2017-12-15). This is
the result.
The diffstat is the same compared to the last revision. It could be
made smaller by sacrificing readibility and breaking the scheme
introduced by the refactoring patch. But I do agree that send-email's
readability could benefit from slicing it into handy functions. And the
refactoring patch reduces the nesting of loops/conditionals.
But it's your code, you decide. I can re-send a fixed-up v2 without the
rebasing.
So long,
- Christian
next reply other threads:[~2018-03-03 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-03 23:58 Christian Ludwig [this message]
2018-03-03 23:58 ` [PATCH v3 1/2] send-email: Rename variable for clarity Christian Ludwig
2018-03-03 23:58 ` [PATCH v3 2/2] send-email: Support separate Reply-To address Christian Ludwig
2018-03-06 8:06 ` git-send-email: Support for Reply-To Junio C Hamano
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180303235814.7241-1-chrissicool@gmail.com \
--to=chrissicool@gmail.com \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).