diff options
| author | Michal Sojka <sojkam1@fel.cvut.cz> | 2015-12-29 22:55:40 +0100 |
|---|---|---|
| committer | David Bremner <david@tethera.net> | 2016-03-14 20:34:17 -0300 |
| commit | 557965b8fae3d7923cee0fb8d9b298173e73a264 (patch) | |
| tree | b4e515f77d92e71adc4d050b56185443f645f92f /notmuch-reply.c | |
| parent | 3dcd6e9a23cb071a5c1bb474180c3b57650df56b (diff) | |
doc/reply: Clarify how reply-to header is handled
Current documentation and comments in the code do not correspond to
the actual code and tests in the test suite ("Un-munging Reply-To" in
T230-reply-to-sender.sh). Fix it.
Diffstat (limited to 'notmuch-reply.c')
| -rw-r--r-- | notmuch-reply.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/notmuch-reply.c b/notmuch-reply.c index 6df54fc9..3c6d685c 100644 --- a/notmuch-reply.c +++ b/notmuch-reply.c @@ -332,7 +332,7 @@ add_recipients_from_message (GMimeMessage *reply, * field and use the From header. This ensures the original sender * will get the reply even if not subscribed to the list. Note * that the address in the Reply-To header will always appear in - * the reply. + * the reply if reply_all is true. */ if (reply_to_header_is_redundant (message)) { reply_to_map[0].header = "from"; |