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] data analysis on plan9
Date: Thu,  9 Jul 2009 21:54:29 -0400	[thread overview]
Message-ID: <34e1c95b52422c59fce9371498e8de04@quanstro.net> (raw)
In-Reply-To: <7d3530220907091849wf230010l991d949a59fb9002@mail.gmail.com>

> http://plan9.bell-labs.com/wiki/plan9/Contrib_index/

the parsing seems a bit odd, at least for my contrib stuff.
contrib/list from contrib(1) does a better job of listing contrib
packages.

- erik



  reply	other threads:[~2009-07-10  1:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09 18:40 hugo rivera
2009-07-09 18:56 ` Federico G. Benavento
2009-07-10  1:40   ` Roman V Shaposhnik
2009-07-10  1:49     ` John Floren
2009-07-10  1:54       ` erik quanstrom [this message]
2009-07-10  6:56     ` Steve Simon
2009-07-09 19:26 ` Jason Catena
2009-07-09 19:34   ` ron minnich
2009-07-09 19:56     ` J. R. Mauro
2009-07-09 19:54 ` J. R. Mauro

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=34e1c95b52422c59fce9371498e8de04@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).