From: "Boyd Roberts" <boyd@fr.inter.net>
To: <9fans@cse.psu.edu>
Subject: [9fans] http://mapage.noos.fr/~repo
Date: Fri, 28 Sep 2001 13:08:39 +0200 [thread overview]
Message-ID: <0a1a01c1480d$ee1c4790$a2b9c6d4@SOMA> (raw)
after months of being slack, and the abandonning of the automated version,
(it was functional, but visually ugly) i've updated:
http://mapage.noos.fr/~repo
to include:
1) my mail which includes russ' mail:
how to do a (floppy) diskless plan 9 install
so it will be publicly available and i won't lose it again.
2) A basic irc bot that evals commands it's given with
the permission & namespace of whoever started it.
http://www.proweb.co.uk/~matt/chugly.rc
my apologies to matt for the delay.
once i get the azerty mess worked out i'll add it too.
and then the bits necessary for the mythical python port.
next reply other threads:[~2001-09-28 11:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 11:08 Boyd Roberts [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-09-28 16:50 Russ Cox
2001-09-28 16:55 ` Jonathan Sergent
2001-09-28 18:56 ` Boyd Roberts
2001-10-01 9:55 ` Douglas A. Gwyn
2001-10-01 10:12 ` Boyd Roberts
2001-04-23 1:45 Boyd Roberts
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='0a1a01c1480d$ee1c4790$a2b9c6d4@SOMA' \
--to=boyd@fr.inter.net \
--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).