From: Nile Geisinger <nile@dloo.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: A different serial port question
Date: Mon, 16 Aug 2004 00:36:41 +0000 [thread overview]
Message-ID: <200408160036.41568.nile@dloo.com> (raw)
Hi Magnus,
Don't think it would work. I need something more interactive for what I'm
working on - a continuous communication channel vs. a discrete one.
I'm really impressed with the tftp work, by the way. It has a number of uses
and adding write support would probably be a great feature for a number of
people (though not for me at the moment).
thanks for the suggestion,
Nile
reply other threads:[~2004-08-16 7:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200408160036.41568.nile@dloo.com \
--to=nile@dloo.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).