From: gsstark@MIT.EDU (Greg Stark)
Subject: Re: Sparse threads
Date: 20 Jan 1996 09:09:33 -0500 [thread overview]
Message-ID: <ycqpwcfvtya.fsf@fierce-bad-rabbit.MIT.EDU> (raw)
In-Reply-To: larsi@ifi.uio.no's message of 20 Jan 1996 06:25:06 +0100
>>>>> Lars Magne Ingebrigtsen writes:
> Uhm. I don't think Gnus should go check the archive group; that would take
> too long. However, you will be able to select these sparse nodes
That sounds pretty cool.
Would this be more feasible if the archive method were a method that had an
overview file? What advantages does nnfolder have?
greg
next prev parent reply other threads:[~1996-01-20 14:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-01-08 12:08 Lars Magne Ingebrigtsen
1996-01-10 18:41 ` Per Abrahamsen
1996-01-11 21:25 ` Lars Magne Ingebrigtsen
1996-01-19 13:15 ` Greg Stark
1996-01-20 5:25 ` Lars Magne Ingebrigtsen
1996-01-20 14:09 ` Greg Stark [this message]
1996-01-20 22:07 ` d. hall
1996-01-22 2:51 ` Lars Magne Ingebrigtsen
1996-01-22 2:51 ` Lars Magne Ingebrigtsen
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=ycqpwcfvtya.fsf@fierce-bad-rabbit.MIT.EDU \
--to=gsstark@mit.edu \
/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).