From: Lennart Jablonka <humm@ljabl.com>
To: Alejandro Colomar <alx@kernel.org>,
Guillem Jover <guillem@hadrons.org>,
linux-man@vger.kernel.org,
Oskari Pirhonen <xxc3ncoredxx@gmail.com>
Subject: Re: Mail-Followup-To header (was: Order priority issues for special 3type sub-section)
Date: Thu, 7 Mar 2024 09:37:43 +0000 [thread overview]
Message-ID: <ZemK5ypK5ccm8w7S@fluorine> (raw)
In-Reply-To: <Zekhz_a9l5ZGwcAb@debian>
Quoth Alejandro Colomar:
>I've found now why my MUAs don't include you in the reply. I've seen
>the following header in your message. I don't know if this is something
>you configured your MUA to send, or if it's an accident. Please have a
>look.
>
>Mail-Followup-To: Alejandro Colomar <alx@kernel.org>,
> Guillem Jover <guillem@hadrons.org>, linux-man@vger.kernel.org
The Mail-Followup-To header field is good and useful. And Mutt,
for example, sends it by default, if you’re properly using `lists`
and `subscribe`. “I’m subscribed to this list anyway, so you need
not send followups to me separately as well.” More people should
use and honor it.
/me unignores mail-followup-to
next prev parent reply other threads:[~2024-03-07 9:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 23:22 Order priority issues for special 3type sub-section Guillem Jover
2024-03-07 0:42 ` Alejandro Colomar
2024-03-07 1:08 ` Oskari Pirhonen
2024-03-07 2:05 ` Alejandro Colomar
2024-03-07 2:09 ` Mail-Followup-To header (was: Order priority issues for special 3type sub-section) Alejandro Colomar
2024-03-07 9:37 ` Lennart Jablonka [this message]
2024-03-07 10:37 ` Alejandro Colomar
2024-03-07 4:06 ` Order priority issues for special 3type sub-section Guillem Jover
2024-03-07 10:24 ` Alejandro Colomar
2024-03-20 9:18 ` Guillem Jover
2024-03-20 10:07 ` Alejandro Colomar
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=ZemK5ypK5ccm8w7S@fluorine \
--to=humm@ljabl.com \
--cc=alx@kernel.org \
--cc=guillem@hadrons.org \
--cc=linux-man@vger.kernel.org \
--cc=xxc3ncoredxx@gmail.com \
/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