9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] [GSOC] auth server: connection refused
Date: Fri, 23 May 2014 14:29:33 -0400	[thread overview]
Message-ID: <393366970af403aeb6a317020ca5a318@ladd.quanstro.net> (raw)
In-Reply-To: <CAAVq3r=-1QmD5nVq0mU=g55Ac0LxpXQMuxr6O90DG_A+ecNghg@mail.gmail.com>

On Fri May 23 14:26:50 EDT 2014, ccuiyyan@gmail.com wrote:

> Finally got the reason.

personally, i preferred the big switch statement in cpurc.  it scales
even to large installations, and has the advantage of being a little
easier to get an overview.  and there's no need for a bunch of files
that are similar to
	#!/bin/rc
	. config-a
- erik



  reply	other threads:[~2014-05-23 18:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23  3:24 yan cui
2014-05-23  4:42 ` yan cui
2014-05-23  7:17   ` Charles Forsyth
2014-05-23 18:25     ` yan cui
2014-05-23 18:29       ` erik quanstrom [this message]
2014-05-23 19:44         ` Steve Simon
2014-05-23 19:49           ` erik quanstrom
2014-05-23  3:26 yan cui

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=393366970af403aeb6a317020ca5a318@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).