Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Re: ding list hosts
Date: 04 May 1999 05:11:21 -0700	[thread overview]
Message-ID: <m3yaj5qbkm.fsf@satellite.local.lan> (raw)
In-Reply-To: Jason L Tibbitts III's message of "02 May 1999 22:30:01 -0500"

Jason L Tibbitts III <tibbs@math.uh.edu> writes:

> >>>>> "HP" == Harry Putnam <reader@newsguy.com> writes:
> 
> HP> My connection to sunsite.auc.dk is almost always very unstable.
> 
> It also bounces a number of messages back to me (the list owner), so it is
> certainly not a complete mirror of the mailing list traffic.
> 
> Honestly, if anyone is gatewaying the list to public newsgroups, I don't
> know about it.  Doing something like that without asking the list
> membership is rather rude.  And propagating such a group is definitely off
> limits.

[Note] Hopefully posting this message to ding list may be useful to
       others.

Thanks for the info...

I'm guessing you may also be involved with the list archive on
sina.hpc.uh.edu.
 
It wasn't clear to me after reading the README on sina /pub how "sina"
can be made to tar.gz (through anonynmous ftp) a
selection of files from the ding-list directory.  There was indication
of tar and gzip  ability, with `get <file>.tar.gz'.  But applying that
to a specific range is where I'm having trouble.

If I wanted to get messages 10001 thru 190001 from "ding-list" 
archive, is it possible, thru ftp, to get those specific messages in a
"tar.gz"file?

Can you coach me a bit on what such a command line would look like
using a plain Gnu ftp client (ftp-0.10-3) or ncftp (ncftp-3.0beta14-1)?


  reply	other threads:[~1999-05-04 12:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-03  2:46 Harry Putnam
1999-05-03  3:30 ` Jason L Tibbitts III
1999-05-04 12:11   ` Harry Putnam [this message]
1999-05-04 14:52     ` Jason L Tibbitts III

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=m3yaj5qbkm.fsf@satellite.local.lan \
    --to=reader@newsguy.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).