From: "boyd, rounin" <boyd@insultant.net>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9ports performance
Date: Wed, 9 Jun 2004 20:44:57 +0200 [thread overview]
Message-ID: <036501c44e51$e0e925f0$9b7f7d50@SOMA> (raw)
In-Reply-To: <ee9e417a040609065746ca3d4f@mail.gmail.com>
> on the other hand, it could be worse. look at gnu grep:
yeah, i'll bet all the time is spent in the arg processing code ;)
prev parent reply other threads:[~2004-06-09 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 17:13 a
2004-05-25 17:56 ` boyd, rounin
2004-05-25 18:14 ` Rob Pike
2004-05-25 22:49 ` Russ Cox
[not found] ` <ee9e417a040609065746ca3d4f@mail.gmail.com>
2004-06-09 18:44 ` boyd, rounin [this message]
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='036501c44e51$e0e925f0$9b7f7d50@SOMA' \
--to=boyd@insultant.net \
--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).