From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] [PATCH] grabrfc: update fetching
Date: Tue, 10 Oct 2023 17:33:12 -0400 [thread overview]
Message-ID: <6E1CDABF412486670BF41501A5F3F98D@eigenstate.org> (raw)
In-Reply-To: <160C282E7085F6F0166F1D36C4D81ABA@smtp.pobox.com>
Quoth Romano <unobe@cpan.org>:
>
> The canonical server for fetching draft RFCs is defunct for ftp access, so a mirror site is now used. Add -d flag to fetch draft RFCs but otherwise do not. When fetching drafts, also fetch index and abstract files. For both normal and draft RFCs, only look for .txt files as there a lot of other files in remote directories that are not relevant.
looks good to me, though we should probably rewrite to fetch over https;
ftp overall is moribund.
prev parent reply other threads:[~2023-10-10 21:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 3:14 Romano
2023-10-10 21:33 ` ori [this message]
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=6E1CDABF412486670BF41501A5F3F98D@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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).