From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] New /prog idea
Date: Mon, 5 May 2014 10:56:56 -0400 [thread overview]
Message-ID: <44d8bf0fa70d84f90ab45e8c5f9eec4a@mikro.quanstro.net> (raw)
In-Reply-To: <5367A270.8070201@lynxline.com>
On Mon May 5 10:40:18 EDT 2014, yshurik@lynxline.com wrote:
> On 05/05/2014 03:06 PM, erik quanstrom wrote:
> > nemo's kernels
>
> What is the nemo kernel? by the way
i used that as a term of art to avoid the fact i messed up by not changing
the name of nix, which in 9atom is quite different, not having the ?C cores.
http://lsub.org/ls/nix.html
- erik
next prev parent reply other threads:[~2014-05-05 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-04 21:59 Oleksandr Iakovliev
2014-05-05 0:53 ` erik quanstrom
2014-05-05 11:03 ` tlaronde
2014-05-05 12:09 ` erik quanstrom
2014-05-05 12:33 ` Charles Forsyth
2014-05-05 13:06 ` erik quanstrom
2014-05-05 14:38 ` Oleksandr Iakovliev
2014-05-05 14:56 ` erik quanstrom [this message]
2014-05-05 15:22 ` Gorka Guardiola
2014-05-05 16:38 ` lucio
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=44d8bf0fa70d84f90ab45e8c5f9eec4a@mikro.quanstro.net \
--to=quanstro@quanstro.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).