From: Alejandro Colomar <alx@kernel.org>
To: 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 11:37:35 +0100 [thread overview]
Message-ID: <ZemY8ArAtGdqScgX@debian> (raw)
In-Reply-To: <ZemK5ypK5ccm8w7S@fluorine>
[-- Attachment #1: Type: text/plain, Size: 1482 bytes --]
Hi Lennart,
On Thu, Mar 07, 2024 at 09:37:43AM +0000, Lennart Jablonka wrote:
> 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.”
Hmm, it's interesting. It messes with what's To and what's Cc, but it's
better than just replying to the list, which I hate because you never
know who's subscribed to it (e.g., most people in the groff@ mailing
list don't send me a copy of their responses, and I'm not subscribed to
the list; or in other lists, even if I'm subscribed to the list, I won't
read most stuff unless either the subject looks interesting or I'm To or
Cc).
> More people should use and honor it.
While I'll keep not using it, I'll honor it, now I understand it. :)
> /me unignores mail-followup-to
Have a lovely day!
Alex
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-03-07 10:37 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
2024-03-07 10:37 ` Alejandro Colomar [this message]
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=ZemY8ArAtGdqScgX@debian \
--to=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