From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] to-do list for plan 9
Date: Tue, 29 Apr 2003 10:55:49 -0400 [thread overview]
Message-ID: <1f09bcb288dd4db6b0b74df6f81bee4d@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304290844450.3977-100000@maxroach.lanl.gov>
> good idea, but how do we get kernel mods in.
You can post them to 9fans or (if they're trivial and not
really worth troubling 9fans with) mail them to 9trouble.
next prev parent reply other threads:[~2003-04-29 14:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 21:58 Fco.J.Ballesteros
2003-04-29 14:49 ` ron minnich
2003-04-29 14:55 ` Russ Cox [this message]
2003-04-29 16:29 ` Christopher Nielsen
2003-04-29 15:39 ` Sam
2003-04-29 15:56 ` andrey mirtchovski
2003-04-29 16:12 ` ron minnich
2003-04-29 16:35 ` Christopher Nielsen
2003-04-30 7:58 ` Fco.J.Ballesteros
2003-04-29 16:28 ` Christopher Nielsen
2003-04-29 16:26 ` Christopher Nielsen
2003-04-30 0:02 ` Boyd Roberts
2003-04-30 0:26 ` ron minnich
2003-04-30 0:41 ` 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=1f09bcb288dd4db6b0b74df6f81bee4d@plan9.bell-labs.com \
--to=rsc@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).