From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: Moving from one server to another
Date: 02 Nov 1995 04:40:52 +0100 [thread overview]
Message-ID: <w8shh0nadkr.fsf_-_@surt.ifi.uio.no> (raw)
In-Reply-To: Felix Lee's message of Mon, 30 Oct 1995 17:28:53 -0800
Felix Lee <flee@teleport.com> writes:
> there really isn't any way around requesting mounds of data. if you
> XOVER to fetch message-IDs for each group, that's reasonably
> efficient.
>
> otherwise, NEWNEWS. oh wait, NEWNEWS only gives you message-ids.
> hmm..
Some server support the "XPAT" (no, wait, it's called something else)
which allows you to say "XPAT MESSAGE-ID 1-1000". Or something like
that. It's very fast when dealing with headers that are in the
.overview files.
--
Home is where the cat is.
next parent reply other threads:[~1995-11-02 3:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199510310129.RAA29350@desiree.teleport.com>
1995-11-02 3:40 ` Lars Magne Ingebrigtsen [this message]
[not found] <w8sd9beoge0.fsf@surt.ifi.uio.no>
[not found] ` <m0tA2pi-000r4TC@main.statsci.com>
[not found] ` <umtohuysc52.fsf@clavicle.cis.ohio-state.edu>
[not found] ` <199510311543.JAA24930@galil.austnsc.tandem.com.>
1995-11-02 3:40 ` 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=w8shh0nadkr.fsf_-_@surt.ifi.uio.no \
--to=larsi@ifi.uio.no \
/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).