From: Richard Miller <rm@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Printenv(1)
Date: Sat, 8 May 2004 12:32:59 +0100 [thread overview]
Message-ID: <7be35434a58a5dc886b2ea12189ce1e3@hamnavoe.com> (raw)
In-Reply-To: <5e7092eca943af584d215efa3a8f1b9c@proxima.alt.za>
> Others may find it useful, I'm sure I should not have reinvented the
> wheel, ...
For a lazier way to get a similar result, try grep '^' /env/*
next prev parent reply other threads:[~2004-05-08 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-08 8:38 lucio
2004-05-08 11:32 ` Richard Miller [this message]
[not found] <ee9e417a040508081457f3fe12@mail.gmail.com>
2004-05-11 18:41 ` rog
2004-05-11 19:06 ` Russ Cox
2004-05-11 19:16 ` rog
2004-05-12 5:18 ` lucio
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=7be35434a58a5dc886b2ea12189ce1e3@hamnavoe.com \
--to=rm@hamnavoe.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).