From: "Brian L. Stuart" <blstuart@bellsouth.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] look, ma, linux's discovered fossil + venti
Date: Thu, 13 Nov 2008 15:17:12 +0000 [thread overview]
Message-ID: <111320081517.24970.491C44F8000C63080000618A22230682229B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net> (raw)
In-Reply-To: <833d65d9d9a65bc668de01aa7a8373a0@coraid.com>
> they have funny names for it all.
> and they're missing the worm part.
>
> http://lwn.net/Articles/305740/
There's a reason for the funny names. If
they don't include the word 'object' enough
times, they'll lose their Tier 1 status in
the buzzword hierarchy.
BLS
next prev parent reply other threads:[~2008-11-13 15:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-13 13:33 erik quanstrom
2008-11-13 15:17 ` Brian L. Stuart [this message]
2008-11-13 16:18 ` ron minnich
2008-11-14 12:08 ` Enrico Weigelt
2008-11-14 12:25 ` Charles Forsyth
2008-11-13 16:26 erik quanstrom
[not found] <1379fbdb80a4315cdc79c0dcf77ca354@quanstro.net>
2008-11-13 16:28 ` ron minnich
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=111320081517.24970.491C44F8000C63080000618A22230682229B0A02D2089B9A019C04040A0DBF9B9D0E9A9B9C040D@att.net \
--to=blstuart@bellsouth.net \
--cc=9fans@9fans.net \
/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).