From: Wes Hardaker <wjhardaker@ucdavis.edu>
Cc: Wes Hardaker <wjhardaker@ucdavis.edu>,
wmperry@aventail.com, ding@gnus.org
Subject: Re: Splitting across backends...
Date: 23 Apr 1999 15:47:58 -0700 [thread overview]
Message-ID: <sdzp3zq7hd.fsf@oakdale.ucdavis.edu> (raw)
In-Reply-To: Simon Josefsson's message of "22 Apr 1999 18:18:34 +0200"
>>>>> On 22 Apr 1999 18:18:34 +0200, Simon Josefsson <jas@pdc.kth.se> said:
Simon> I wrote a `nnagent-request-set-mark', similar to your second
Simon> solution, some time ago. It stashes flag setting requests to a
Simon> file, when you become plugged you `eval-buffer' the file. It
Simon> should be trivial to plug it into Gnus. I'll see what I can
Simon> do...
Cool! I vaguely recall seeing you post this to the nnimap list
earlier today (a group I haven't read yet). I'll be trying it out
shortly, thanks a bunch!
--
"Ninjas aren't dangerous. They're more afraid of you than you are of them."
next prev parent reply other threads:[~1999-04-23 22:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-21 18:00 William M. Perry
1999-04-21 23:15 ` Wes Hardaker
1999-04-22 15:07 ` Kai.Grossjohann
1999-04-22 16:18 ` Simon Josefsson
1999-04-23 22:47 ` Wes Hardaker [this message]
1999-04-22 16:09 ` Simon Josefsson
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=sdzp3zq7hd.fsf@oakdale.ucdavis.edu \
--to=wjhardaker@ucdavis.edu \
--cc=ding@gnus.org \
--cc=wmperry@aventail.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).