From: presotto@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] serial port programming
Date: Thu, 15 Feb 2001 16:47:19 -0500 [thread overview]
Message-ID: <20010215214721.C4EA819A15@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 104 bytes --]
Guess he'll have to wait till next release then...
I'll put the current version on the update page.
[-- Attachment #2: Type: message/rfc822, Size: 1225 bytes --]
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] serial port programming
Date: Thu, 15 Feb 2001 22:37:39 0000
Message-ID: <20010215213250.DC734199D5@mail.cse.psu.edu>
> look at /sys/src/cmd/ip/ppp/ppp.c:2437,2451
a pity that file only has 2433 lines...
next reply other threads:[~2001-02-15 21:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 21:47 presotto [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-16 4:41 anothy
2001-02-15 22:37 rog
2001-02-15 21:24 presotto
2001-02-15 17:18 nigel
2001-02-15 17:35 ` Sam Ducksworth
2001-02-15 17:10 Sam Ducksworth
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=20010215214721.C4EA819A15@mail.cse.psu.edu \
--to=presotto@plan9.bell-labs.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).