From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: MFT and Gcc
Date: Sat, 20 Oct 2001 00:30:02 +0200 [thread overview]
Message-ID: <vafzo6nqn4l.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <87adyns3tv.fsf@harpo.homeip.net> (Samuel Padgett's message of "Fri, 19 Oct 2001 17:43:56 -0400")
Samuel Padgett <spadgett1@nc.rr.com> writes:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>> WIBNI the MFT generation code could be extended to delete the Gcc
>> header, if the message goes to self anyway?
>
> But what if I Gcc a different group?
Right. Then the header should not be deleted.
But remember that I wanted a user option, turned off by default. So
you don't need to be afraid that Gnus will begin to eat your Gcc
headers behind your back!
kai
--
GNU/Linux provides a nice `poweroff' command, but where is `poweron'?
next prev parent reply other threads:[~2001-10-19 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-19 21:30 Kai Großjohann
2001-10-19 21:43 ` Samuel Padgett
2001-10-19 22:30 ` Kai Großjohann [this message]
2001-10-20 10:14 ` Per Abrahamsen
2001-10-21 5:15 ` Karl Eichwalder
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=vafzo6nqn4l.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).