From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] 9p on Yeeloong (gNewSense Linux)
Date: Wed, 1 Jul 2009 08:47:56 +0100 [thread overview]
Message-ID: <9bd43ea1cac84ec9fcaa2541d1f7b0d6@hamnavoe.com> (raw)
In-Reply-To: <eb54d142db171a0b14998e133f08d4a3@proxima.alt.za>
> lucio@proxima.alt.za:
> but I know that I haven't yet
> found a CPU architecture I dislike more then the Intel i386
Ever tried the 6502?
next prev parent reply other threads:[~2009-07-01 7:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 5:31 Akshat Kumar
2009-06-29 9:10 ` lucio
2009-07-01 7:47 ` Richard Miller [this message]
[not found] <32d9733a263818587ab347169fd8a312@quanstro.net>
2009-06-29 17:29 ` lucio
2009-06-29 17:39 ` erik quanstrom
2009-06-29 17:59 ` lucio
-- strict thread matches above, loose matches on Subject: below --
2009-06-29 4:55 lucio
2009-06-29 5:41 ` ron minnich
2009-06-29 8:49 ` lucio
2009-06-29 12:14 ` erik quanstrom
2009-06-29 15:03 ` Eric Van Hensbergen
2009-06-29 17:37 ` Skip Tavakkolian
2009-07-02 11:33 ` Uriel
2009-07-02 11:34 ` Uriel
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=9bd43ea1cac84ec9fcaa2541d1f7b0d6@hamnavoe.com \
--to=9fans@hamnavoe.com \
--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).