From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: mail/post forwarding now has an option to forward all original headers
Date: Thu, 14 Dec 2023 13:09:39 +0000 [thread overview]
Message-ID: <87fs05gcbw.fsf@ucl.ac.uk> (raw)
In-Reply-To: <874jgn2ros.fsf@dataswamp.org>
It's probably due to Eric's post having "Mail-Followup-To" set to the
list so any reply will not include him?
--
Eric S Fraga via gnus (Emacs 30.0.50 2023-07-11) on Debian bullseye/sid
prev parent reply other threads:[~2023-12-14 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 18:05 Eric Abrahamsen
2023-12-12 18:37 ` Emanuel Berg
2023-12-13 20:41 ` Eric Abrahamsen
2023-12-14 10:45 ` Emanuel Berg
2023-12-15 1:42 ` Eric Abrahamsen
2023-12-17 17:19 ` Emanuel Berg
2023-12-14 13:09 ` Eric S Fraga [this message]
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=87fs05gcbw.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=ding@gnus.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).