From: Dave Lukes <davel@anvil.com>
To: 9fans <9fans@cse.psu.edu>
Subject: Re: [9fans] 9conlon: [Fwd: RE: internet in the upper hall]
Date: Wed, 7 Apr 2004 14:45:16 +0100 [thread overview]
Message-ID: <1081345516.4565.584.camel@zevon> (raw)
In-Reply-To: <6ffba97b9fd3467d67d2d5cbbf07ba83@juice.thebigchoice.com>
On Tue, 2004-04-06 at 18:43, matt@proweb.co.uk wrote:
> yup, got an 802.11b router here
>
> and a 16 port 10/100 switch
Excellent!
Anvil's office is within 10 mins bike ride,
so I can always whiz over there to make up cables if necc.
Matt,
Will you need a hand lugging stuff from St. Pancras?
If so (and if I've still got my car then:-),
a lift might be arranged, or a cheap(er) local taxi ...
Cheers,
Dave.
next prev parent reply other threads:[~2004-04-07 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-06 16:29 Dave Lukes
2004-04-06 16:53 ` boyd, rounin
2004-04-06 17:24 ` Eric KD5UWL
2004-04-06 17:36 ` andrey mirtchovski
2004-04-06 22:56 ` Eric KD5UWL
2004-04-07 1:58 ` boyd, rounin
2004-04-06 17:43 ` matt
2004-04-07 13:45 ` Dave Lukes [this message]
2004-04-07 13:56 ` matt
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=1081345516.4565.584.camel@zevon \
--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).