From: SHRIZZA <shrizza@gmail.com>
To: Plan 9 Fans <9fans@cse.psu.edu>
Subject: [9fans] Whoops
Date: Mon, 20 Mar 2006 08:28:24 +0900 [thread overview]
Message-ID: <2E2AE90F-DA52-4448-BBD3-9B4BA623E2ED@gmail.com> (raw)
Sorry about that email I just sent. I accidentally sent a draft that
I had composed about 2 or 3 weeks ago but I've had progress since
then. Still can't get it to boot though cause of faulty hardware.
next reply other threads:[~2006-03-19 23:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-19 23:28 SHRIZZA [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-25 23:07 Dan Cross
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=2E2AE90F-DA52-4448-BBD3-9B4BA623E2ED@gmail.com \
--to=shrizza@gmail.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).