From: "Lakshman N. Yagati" <ynl@research.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rxmitproc
Date: Wed, 31 Jul 2002 08:57:40 -0400 [thread overview]
Message-ID: <3D47DEC4.CAA8EFFB@research.bell-labs.com> (raw)
In-Reply-To: <ee9b0520bb5f7c62c865ec81c724c383@plan9.bell-labs.com>
Russ is right. I left the message by accident. It has been
removed.
- ynl
Russ Cox wrote:
> it means the arp retransmit proc has been started.
> it's a debugging print from the ipv6 transition, i believe.
>
> russ
next prev parent reply other threads:[~2002-07-31 12:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 4:25 Russ Cox
2002-07-31 12:57 ` Lakshman N. Yagati [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-31 6:13 okamoto
2002-07-31 4:08 okamoto
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=3D47DEC4.CAA8EFFB@research.bell-labs.com \
--to=ynl@research.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).