From: Matt Armstrong <matt@lickey.com>
Subject: Re: Auto gen of MFT header for "unsubscribed" lists. (patch)
Date: Tue, 05 Feb 2002 10:29:59 -0700 [thread overview]
Message-ID: <87ofj33kh4.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <87ofj4cm0w.fsf@cs.utah.edu> (Karra's message of "Tue, 05 Feb 2002 15:02:06 +0530")
Karra <karra@cs.utah.edu> writes:
> C-c C-f C-m inserts an empty MFT header. The following patch
> introduces a new function and key binding C-c C-f C-a that will insert
> a MFT header containing the address in the To field and the user's
> mail address.
>
> This should be helpful when sending mails to lists one is not
> subscribed to.
I'm not opposed to this patch (more features good ugh grunt ugh!) but
when there is no MFT header, the default reply-to behavior is supposed
to be used, which includes the sender and any recipients. In other
words, message-gen-unsubscribed-mft inserts what is the default
anyway.
Have you found cases where this is necessary?
--
matt
next prev parent reply other threads:[~2002-02-05 17:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 9:32 Karra
2002-02-05 16:48 ` ShengHuo ZHU
2002-02-05 17:29 ` Matt Armstrong [this message]
2002-02-06 10:33 ` Karra
2002-02-06 17:00 ` Paul Jarc
2002-02-07 16:52 ` Matt Armstrong
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=87ofj33kh4.fsf@squeaker.lickey.com \
--to=matt@lickey.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;
as well as URLs for NNTP newsgroup(s).