From: "lartc@manchotnetworks.net" <lartc@manchotnetworks.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] testing high delay tcp
Date: Sat, 10 May 2003 16:59:15 +0000 [thread overview]
Message-ID: <marc-lartc-105258562032470@msgid-missing> (raw)
In-Reply-To: <marc-lartc-105250701117961@msgid-missing>
Stef,
It would be my pleasure, although I have been spending most of my day on
an rtc problem -- nist prefers it to be modular, and red hat doesn't.
Cheers
Charles
On Sat, 2003-05-10 at 13:25, Stef Coene wrote:
> On Saturday 10 May 2003 10:16, lartc@manchotnetworks.net wrote:
> > Hi Stef,
> >
> > Just perfect. Marvelous.
> Do you mind keeping me informed about the test results? I'm curious to know
> if NIST works like you expected.
>
> Stef
>
> --
>
> stef.coene@docum.org
> "Using Linux as bandwidth manager"
> http://www.docum.org/
> #lartc @ irc.oftc.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-05-10 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 19:06 [LARTC] testing high delay tcp lartc
2003-05-09 19:37 ` Stef Coene
2003-05-10 16:59 ` lartc [this message]
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=marc-lartc-105258562032470@msgid-missing \
--to=lartc@manchotnetworks.net \
--cc=lartc@vger.kernel.org \
/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