From: geoff@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] papers return to plan9.bell-labs.com
Date: Thu, 31 Aug 2006 23:55:49 -0400 [thread overview]
Message-ID: <95a4c8f7a21cf03bfcfd29ca1f9b6ec0@plan9.bell-labs.com> (raw)
In-Reply-To: <64c27994f04b80a82d2e978ca383bf5a@plan9.bell-labs.com>
This time for sure. Our mechanism for maintaining the copy of
/sys/doc seen at plan9.bell-labs.com is sub-optimal. (It's also not
obvious to me why this is different from /n/sources/plan9/sys/doc.)
After some formatting, copying and hand editing, all the papers are
present in all formats (except that there's no HTML version of the
troff manual). I have just clicked on every hyperlink on the paper
page; they are all live currently. We may have some machinery that is
nuking html or just index.html files, so I'll keep an eye on
index.html.
prev parent reply other threads:[~2006-09-01 3:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 1:17 geoff
2006-09-01 3:55 ` geoff [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=95a4c8f7a21cf03bfcfd29ca1f9b6ec0@plan9.bell-labs.com \
--to=geoff@plan9.bell-labs.com \
--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).