From: Dave Lukes <davel@anvil.com>
To: 9fans <9fans@cse.psu.edu>
Subject: [9fans] [Fwd: internet in the upper hall]
Date: Fri, 2 Apr 2004 16:04:59 +0100 [thread overview]
Message-ID: <1080918299.1704.1696.camel@rea> (raw)
[-- Attachment #1: Type: text/plain, Size: 122 bytes --]
YeeeHaw!!!
(I was having a crap day until now:-~).
Now I have to go haggle with my kid brother!
Cheers,
Dave.
[-- Attachment #2: Forwarded message - internet in the upper hall --]
[-- Type: message/rfc822, Size: 1593 bytes --]
From: "Adrian" <ade@unionchapel.org.uk>
To: "'Dave Lukes'" <davel@anvil.com>
Subject: internet in the upper hall
Date: Fri, 2 Apr 2004 11:11:35 +0100
Message-ID: <000701c4189a$e2116ec0$0200a8c0@union3jyb188p1>
Further to our conversations about your may hire, I can get you a broadband
connection in the upper hall -
What price had we previously discussed?
x
A
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.615 / Virus Database: 394 - Release Date: 08/03/2004
next reply other threads:[~2004-04-02 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-02 15:04 Dave Lukes [this message]
2004-04-02 15:56 ` boyd, rounin
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=1080918299.1704.1696.camel@rea \
--to=davel@anvil.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).