From: Kai Grossjohann <kai@emptydomain.de>
Subject: Re: How to avoid resent- headers?
Date: Mon, 19 Jan 2004 21:43:33 +0100 [thread overview]
Message-ID: <87llo3brey.fsf@emptyhost.emptydomain.de> (raw)
In-Reply-To: <87n08kng8x.fsf@home.lan>
Steinar Bang <sb@dod.no> writes:
> How do I avoid the resent-from etc. headers in resent messages?
This is like asking how to avoid From/To/Cc in normal messages ;-)
Kai
next prev parent reply other threads:[~2004-01-19 20:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 14:51 Steinar Bang
2004-01-19 20:43 ` Kai Grossjohann [this message]
2004-01-19 22:34 ` Steinar Bang
2004-01-19 23:30 ` Jesper Harder
2004-01-20 6:13 ` Steinar Bang
2004-01-20 14:06 ` Josh Huber
2004-01-20 19:37 ` Steinar Bang
2004-01-20 8:47 ` Kai Grossjohann
2004-01-20 19:39 ` Steinar Bang
2004-01-21 10:02 ` Kai Grossjohann
[not found] ` <7cd69fiipf.fsf@nature.tsukuba.ac.jp>
2004-01-20 0:25 ` Katsumi Yamaoka
2004-01-20 6:20 ` Steinar Bang
[not found] ` <87smibm997.fsf-0MSThuzptbI@public.gmane.org>
2004-01-20 21:43 ` Jochen Küpper
2004-01-20 6:24 ` Steinar Bang
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=87llo3brey.fsf@emptyhost.emptydomain.de \
--to=kai@emptydomain.de \
/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).