From: Sten Drescher <dreschs@mpd.tandem.com>
Subject: Double citation headers in Gnus.
Date: Mon, 6 Nov 1995 15:46:42 -0600 (CST) [thread overview]
Message-ID: <55vioxo1q7.fsf@galil.austnsc.tandem.com> (raw)
The following message is a courtesy copy of an article
that has been posted as well.
When I followup to messages, I get two citation headers: One
trhat I select (via supercite's electric references), and one that looks
like (but isn't quite) supersite's inarticle-writes header style. Does
anyone know why it's doing this, and how can I stop it?
--
#include <disclaimer.h> /* Sten Drescher */
To get my PGP public key, send me email with your public key and
Subject: PGP key exchange
Key fingerprint = 90 5F 1D FD A6 7C 84 5E A9 D3 90 16 B2 44 C4 F3
next reply other threads:[~1995-11-06 21:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-11-06 21:46 Sten Drescher [this message]
1995-11-06 23:15 ` Christopher Davis
1995-11-07 17:30 ` Sten Drescher
[not found] <199511071730.LAA22954@galil.austnsc.tandem.com.>
1995-11-07 20:43 ` Edward J. Sabol
1995-11-07 22:32 ` Christopher Davis
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=55vioxo1q7.fsf@galil.austnsc.tandem.com \
--to=dreschs@mpd.tandem.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).