From: Paul J Collins <sneakums@sto-kerrig.org>
Subject: Re: Mail-Followup-To interaction with gnus-summary-followup
Date: 23 Feb 2001 19:50:01 +0000 [thread overview]
Message-ID: <87g0h5mb6n.fsf@sto-kerrig.org> (raw)
In-Reply-To: <m31ysv1t3c.fsf@multivac.student.cwru.edu>
>>>>> "PJ" == Paul Jarc <prj@po.cwru.edu> writes:
PJ> Ok, here's the fix (against current CVS). For real, this
PJ> time. :)
That works great, thank you.
--
Paul Collins <sneakums@sto-kerrig.org> - - - [ ]
GPG: 0A49 49A9 2932 0EE5 89B2 9EE0 3B65 7154 8131 1BCD
"This one's optimistic, this one went to market;
this one just came out of the swamp."
next prev parent reply other threads:[~2001-02-23 19:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-11 14:42 Paul J Collins
2001-02-11 15:02 ` ShengHuo ZHU
2001-02-11 15:12 ` Peter Makholm
2001-02-11 15:38 ` Paul J Collins
2001-02-11 18:05 ` Kai Großjohann
2001-02-11 19:38 ` Paul Jarc
2001-02-16 19:51 ` Paul J Collins
2001-02-17 20:34 ` Paul Jarc
2001-02-17 21:03 ` ShengHuo ZHU
2001-02-18 0:50 ` Paul J Collins
2001-02-18 15:38 ` Per Abrahamsen
2001-02-18 17:06 ` Paul J Collins
2001-02-18 23:14 ` Paul Jarc
2001-02-19 1:14 ` ShengHuo ZHU
2001-02-23 19:50 ` Paul J Collins [this message]
2001-02-11 14:49 Paul J Collins
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=87g0h5mb6n.fsf@sto-kerrig.org \
--to=sneakums@sto-kerrig.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).