From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Cc: inferno-list@vitanuova.com
Subject: Re: [9fans] devip connect error state
Date: Wed, 8 Aug 2007 14:14:26 -0700 [thread overview]
Message-ID: <13426df10708081414n279616b8vd6deb628da8ee8bd@mail.gmail.com> (raw)
In-Reply-To: <a4e6962a0708081359n32d8bcc2ic9ba2af4c57a271a@mail.gmail.com>
On 8/8/07, Eric Van Hensbergen <ericvh@gmail.com> wrote:
> So, bug or feature? At the very least it would seem a good idea to
> set c->state to Hungup (and also change the c->state != 0 to a
> c->state != Idle). I have no idea why we set c->state to Connected in
> Inferno hosted -- that just seems completely bonkers.
It actually looks like a cut and paste error -- cut, paste, forget to
change the rvalue.
ron
next prev parent reply other threads:[~2007-08-08 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 20:59 Eric Van Hensbergen
2007-08-08 21:14 ` ron minnich [this message]
2007-08-08 21:19 ` Charles Forsyth
2007-08-09 3:33 ` Eric Van Hensbergen
2007-08-09 6:47 ` Bruce Ellis
2007-08-09 8:38 ` Charles Forsyth
2007-08-08 21:48 ` Charles Forsyth
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=13426df10708081414n279616b8vd6deb628da8ee8bd@mail.gmail.com \
--to=rminnich@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=inferno-list@vitanuova.com \
/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).