From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: [9fans] updates
Date: Thu, 13 May 2004 15:39:57 -0400 [thread overview]
Message-ID: <ab10e1060377d759ebf8f7dcab368b66@plan9.bell-labs.com> (raw)
i've pushed out a bunch of updates to sources that had
been sitting around for a while. it's possible i missed
some dependancies so mail 9trouble if you find anything
amiss. thanks to brucee for the vlong optimised 8c.
--jim
next reply other threads:[~2004-05-13 19:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-13 19:39 jmk [this message]
2004-05-13 19:58 ` andrey mirtchovski
-- strict thread matches above, loose matches on Subject: below --
2002-11-07 16:47 Russ Cox
2001-12-11 16:39 [9fans] Updates Russ Cox
2001-12-11 12:19 Ramon Poca
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=ab10e1060377d759ebf8f7dcab368b66@plan9.bell-labs.com \
--to=jmk@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).