From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /n/sources timeout
Date: Wed, 14 Mar 2007 06:36:08 +0200 [thread overview]
Message-ID: <33d7d22c8efcd33abfa71ae135b5b19b@proxima.alt.za> (raw)
In-Reply-To: <ae9679470703131548v63d2c62cof81804faab220a95@mail.gmail.com>
> While sources is up, the sources website is still down.
>
> As an example of how terrible this is, Donald Knuth cannot read the
> semi-humorous README file I wrote about using the Computer Modern
> typeface with troff(1).
>
> <http://cm.bell-labs.com/sources/contrib/btdn/lib/cm/README>
Yep. I get:
term% hget http://cm.bell-labs.com/sources/contrib/btdn/lib/cm/README | htmlfmt
hget: Server choked
++L
next prev parent reply other threads:[~2007-03-14 4:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-12 16:43 Philip Dye
2007-03-12 16:57 ` Skip Tavakkolian
2007-03-12 20:53 ` geoff
2007-03-13 22:48 ` Benn Newman
2007-03-14 4:36 ` lucio [this message]
2007-03-14 20:19 ` geoff
2007-03-14 20:25 ` erik quanstrom
2007-03-14 20:25 ` Francisco J Ballesteros
2007-03-14 20:53 ` geoff
-- strict thread matches above, loose matches on Subject: below --
2007-03-12 16:03 Philip Dye
2007-03-12 16:10 ` Russ Cox
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=33d7d22c8efcd33abfa71ae135b5b19b@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.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).