From: Alexander Viro <viro@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] design issues in operating systems
Date: Tue, 4 Dec 2001 16:59:07 -0500 [thread overview]
Message-ID: <Pine.GSO.4.21.0112041646440.21188-100000@binet.math.psu.edu> (raw)
In-Reply-To: <200112041905.OAA14111@augusta.math.psu.edu>
On Tue, 4 Dec 2001, Dan Cross wrote:
> In article <Pine.GSO.4.21.0112031647410.17686-100000@binet.math.psu.edu> you write:
> >Hmm... I doubt that "for everyone to contribute" is a good thing,
> >but seeing is a different story...
>
> Nonsense. Everyong is free to contribute. But, contribution is not
> synonymous with acceptance.
<shrug> well, provided that your .procmailrc is well-maintained - sure.
You _really_ don't want to see the... contributions from Qlogics SCSI
folks. Or Intel folks who do NIC drivers. There are less harmful ways
to take a second look at your last meal...
> The labs might run into another problem if development source is there
> for all to pick at. Surely they will receive a ton of patches for things
> that they're already aware of, have already fixed but not synced to the
> outside fileserver, or are still experimental and changing rapidly. The
> cost in terms of time and resources to sift through what comes in from
> the outside could be non-trivial.
_That_ is easy to deal with -
/* XXX: Yes, I know. It's crap. Working on that. */
is usually enough for stuff that stays for a week or so and for very
recent breakage you have not too may places you've just touched, so
sorting is not a big deal...
next prev parent reply other threads:[~2001-12-04 21:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-03 21:34 rob pike
2001-12-03 22:01 ` Alexander Viro
2001-12-04 19:05 ` Dan Cross
2001-12-04 21:59 ` Alexander Viro [this message]
2001-12-07 9:36 ` Barry
-- strict thread matches above, loose matches on Subject: below --
2001-12-05 8:49 Fco.J.Ballesteros
2001-12-04 17:27 erik quanstrom
2001-12-04 10:36 forsyth
2001-12-03 22:50 jmk
2001-12-03 21:31 rob pike
2001-12-03 16:27 presotto
2001-12-03 16:07 anothy
2001-12-03 16:04 ` Lucio De Re
2001-12-03 15:45 bwc
2001-12-03 14:49 bwc
2001-12-02 17:05 Andrey A Mirtchovski
2001-12-03 10:09 ` josh d
2001-12-03 15:24 ` Ronald G Minnich
2001-12-03 15:08 ` Lucio De Re
2001-12-03 15:48 ` andrey
2001-12-03 18:03 ` Ozan Yigit
2001-12-03 20:51 ` Mike Haertel
2001-12-03 10:10 ` north_
2001-12-03 16:55 ` John S. Dyson
2001-12-05 9:56 ` Douglas A. Gwyn
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=Pine.GSO.4.21.0112041646440.21188-100000@binet.math.psu.edu \
--to=viro@math.psu.edu \
--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).