From: Peter Wang <novalazy@gmail.com>
To: Jani Nikula <jani@nikula.org>
Cc: notmuch@notmuchmail.org
Subject: Re: [RFC PATCH 3/3] cli: support Mail-Followup-To: in notmuch reply
Date: Wed, 6 Mar 2013 22:08:49 +1100 [thread overview]
Message-ID: <20130306220849.GB5730@hili.localdomain> (raw)
In-Reply-To: <871ubwdcy7.fsf@nikula.org>
On Sun, 03 Mar 2013 11:56:00 +0200, Jani Nikula <jani@nikula.org> wrote:
> I have added the reply.honor_followup_to configuration because, although
> widely used, it's not a standard, and therefore some people might not
> like to respect that. Although I'd argue if the sender of the message
> has added that header, it's the sender's wish it should be respected.
>
> If people think our reply-all should always and unconditionally respect
> Mail-Followup-To if it's present, I'd be happy to throw out the config
> option. It's ugly.
How about making it it optional on the command-line rather than through
configuration? Then you don't lose the functionality where you can
initiate a reply to all visible From/To/Cc addresses (ready for pruning),
regardless of the value of some header you probably don't even see, even
if typically you *do* want to respect that header.
(Bringing us back to the three reply functions.)
Peter
next prev parent reply other threads:[~2013-03-06 11:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 19:55 [RFC PATCH 1/3] cli: cosmetic style cleanup Jani Nikula
2013-03-02 19:55 ` [RFC PATCH 2/3] cli: add reply.honor_followup_to configuration option Jani Nikula
2013-03-02 19:55 ` [RFC PATCH 3/3] cli: support Mail-Followup-To: in notmuch reply Jani Nikula
2013-03-03 1:07 ` Peter Wang
2013-03-03 9:56 ` Jani Nikula
2013-03-06 11:08 ` Peter Wang [this message]
2013-03-29 14:13 ` [RFC PATCH 1/3] cli: cosmetic style cleanup David Bremner
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: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130306220849.GB5730@hili.localdomain \
--to=novalazy@gmail.com \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.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).