From: "Bruce Ellis" <brucee@chunder.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Bruce
Date: Fri, 14 Nov 2003 09:46:33 +1100 [thread overview]
Message-ID: <01be01c3aa39$679ebd20$8201a8c0@cc77109e> (raw)
In-Reply-To: <b716b9ce41f68806fdf3a24972700f10@9srv.net>
sounds like a good day to visit woolloomooloo, tho there still isn't
a university there.
brucee
----- Original Message -----
From: <a@9srv.net>
To: <9fans@cse.psu.edu>
Sent: Thursday, November 13, 2003 10:33 PM
Subject: Re: [9fans] Bruce
> okay, so Michael Baldwin (the one who post here once in a
> while) == Bruce, boyd == Susan, and i suppose ("to avoid
> confusion") Bruce Ellis == brucee.
>
> this is gonna be fun. :-)
next parent reply other threads:[~2003-11-13 22:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b716b9ce41f68806fdf3a24972700f10@9srv.net>
2003-11-13 22:46 ` Bruce Ellis [this message]
2003-11-11 2:30 [9fans] FS question bruce
2003-11-11 12:28 ` Lucio De Re
2003-11-12 19:55 ` Andrew Simmons
2003-11-12 21:16 ` boyd, rounin
2003-11-13 0:34 ` [9fans] Bruce Michael Baldwin
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='01be01c3aa39$679ebd20$8201a8c0@cc77109e' \
--to=brucee@chunder.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).