From: Artem Pylypchuk <articice@ua.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] 9fans Digest, Vol 70, Issue 42
Date: Fri, 26 Feb 2010 14:38:25 +0200 [thread overview]
Message-ID: <201002261438.25809.articice@ua.fm> (raw)
In-Reply-To: <mailman.10191.1266963822.1513.9fans@9fans.net>
> Date: Tue, 23 Feb 2010 10:27:51 -0800
> From: Russ Cox <rsc@swtch.com>
> Subject: Re: [9fans] pppoe on Plan 9
> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
> Message-ID:
> <dd6fe68a1002231027r6ad74c72w2751e2a081e390d8@mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> i understand the protocol.
> but if there is no -S option given, the current code
> waits for an offer with service name == "".
> that's silly. it should take the first one it gets.
>
> russ
Not sure, what's worse - waiting for an empty service name or accepting the
first one available. I'm more into how it is: didn't specify an -S option -
then it's empty -> accept empty service name.
parent reply other threads:[~2010-02-26 12:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <mailman.10191.1266963822.1513.9fans@9fans.net>]
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=201002261438.25809.articice@ua.fm \
--to=articice@ua.fm \
--cc=9fans@9fans.net \
/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).