From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: gnus-boring-article-headers suggestion
Date: 18 Jan 2001 16:31:05 -0500 [thread overview]
Message-ID: <5bn1coa6p2.fsf@avocet.cs.rochester.edu> (raw)
In-Reply-To: <8766jfi8eu.fsf@lovi.inf.elte.hu> (NAGY Andras's message of "16 Jan 2001 20:50:01 +0100")
NAGY Andras <nagya@inf.elte.hu> writes:
> Following the pattern introduced by the `newsgroups' element, namely:
>
> `newsgroups'
> Remove the `Newsgroups' header if it only contains the current
> group name.
>
>
> I suggest having a `to' element available as well:
>
> `to'
> Remove the `To' header if it only contains the value of the current
> group's `to-address' parameter.
Done, but I name it `to-address'.
ShengHuo
next prev parent reply other threads:[~2001-01-18 21:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 19:50 NAGY Andras
2001-01-17 8:45 ` importing mails from other gnus Dirk Gomez
2001-01-17 9:17 ` Kai Großjohann
2001-01-18 21:31 ` ShengHuo ZHU [this message]
2001-01-18 21:50 ` gnus-boring-article-headers suggestion NAGY Andras
2001-01-19 1:12 ` Karl Kleinpaste
2001-01-19 1:27 ` ShengHuo ZHU
2001-01-19 2:14 ` Karl Kleinpaste
2001-01-19 14:27 ` David S. Goldberg
2001-02-19 17:21 ` another " NAGY Andras
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=5bn1coa6p2.fsf@avocet.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/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).