From: "Christopher Nielsen" <cnielsen@pobox.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] requesting more information about the Gsoc project
Date: Wed, 21 Mar 2007 12:51:02 -0700 [thread overview]
Message-ID: <e0ac85f90703211251t3da64bbex8980ce39f26c7818@mail.gmail.com> (raw)
In-Reply-To: <9fa13fe80f07090dbdca461966c11d09@coraid.com>
On 3/21/07, erik quanstrom <quanstro@coraid.com> wrote:
> i don't know of any particular complaints with the functionality of 9load.
i don't think the complaints have anything to do with functionality. i
think it's more maintainability. you're maintaining drivers in two
separate places, which is tedious and error prone.
--
Christopher Nielsen
"They who can give up essential liberty for temporary
safety, deserve neither liberty nor safety." --Benjamin Franklin
prev parent reply other threads:[~2007-03-21 19:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 9:15 Rajika Kumarasiri
2007-03-21 11:56 ` erik quanstrom
2007-03-21 11:58 ` erik quanstrom
2007-03-21 12:40 ` [9fans] " Darren Bane
2007-03-21 19:51 ` Christopher Nielsen [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=e0ac85f90703211251t3da64bbex8980ce39f26c7818@mail.gmail.com \
--to=cnielsen@pobox.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).