From: Wes Hardaker <wjhardaker@ucdavis.edu>
Cc: ding@gnus.org
Subject: Re: Split replies to go with originals
Date: 13 Nov 1998 09:14:45 -800 [thread overview]
Message-ID: <x7n25vms56.fsf@des.castles.com> (raw)
In-Reply-To: Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "11 Nov 1998 20:59:54 +0100"
>>>>> On 11 Nov 1998 20:59:54 +0100, Kai.Grossjohann@CS.Uni-Dortmund.DE said:
Kai> You manually put a message in the foo group (using B m, say).
Kai> Now, you get a reply for that message, and naturally, you want to
Kai> put it in the foo group, too. Here's some code which does this
Kai> if you have nnmail-treat-duplicates set to a non-nil value and if
Kai> you use nnmail-split-fancy.
Ok. I'll bite. I love loosing mail. Wish me luck. :-)
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next prev parent reply other threads:[~1998-11-13 17:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-11 19:59 Kai.Grossjohann
1998-11-12 11:02 ` Terje Sannum
1998-11-12 11:14 ` Kai.Grossjohann
1998-11-12 22:42 ` Terje Sannum
1998-11-13 17:14 ` Wes Hardaker [this message]
1998-11-13 22:20 ` Kai.Grossjohann
1998-11-13 22:39 ` Kai.Grossjohann
1999-01-28 18:35 Kai.Grossjohann
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=x7n25vms56.fsf@des.castles.com \
--to=wjhardaker@ucdavis.edu \
--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).