9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] THX hell
Date: Tue,  1 May 2007 19:46:53 +0100	[thread overview]
Message-ID: <5f8ca9cf01a0f1c6a2fab53a1062152e@hamnavoe.com> (raw)
In-Reply-To: <13426df10705011142s943fa15leee215f5bbe0ab4c@mail.gmail.com>

> any ideas here? What makes sense?

4. Use the T41 instead.



  reply	other threads:[~2007-05-01 18:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-01 18:42 ron minnich
2007-05-01 18:46 ` Richard Miller [this message]
2007-05-01 18:52   ` ron minnich
2007-05-01 20:59 ` geoff
2007-05-01 21:40 ` Bakul Shah
2007-05-01 21:45   ` ron minnich
2007-05-01 22:14   ` Steve Simon
2007-05-02  0:24     ` ron minnich
2007-05-02  0:29       ` Eric Van Hensbergen
2007-05-02  9:14 ` csant
2007-05-02 17:00   ` ron minnich
2007-05-02 17:28     ` Anthony Sorace
2007-05-02 17:45       ` W B Hacker
2007-05-03  7:23         ` csant
2007-05-02 22:26     ` csant

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=5f8ca9cf01a0f1c6a2fab53a1062152e@hamnavoe.com \
    --to=9fans@hamnavoe.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).