From: Lucio De Re <lucio@proxima.alt.za>
To: "rob pike, esq." <rob@plan9.bell-labs.com>
Cc: 9fans@cse.psu.edu
Subject: Re: [9fans] du
Date: Thu, 21 Mar 2002 15:44:27 +0200 [thread overview]
Message-ID: <20020321154427.H9019@cackle.proxima.alt.za> (raw)
In-Reply-To: <9ac634e947eb39000123f84271f9c74e@plan9.bell-labs.com>; from rob pike, esq. on Thu, Mar 21, 2002 at 08:37:26AM -0500
On Thu, Mar 21, 2002 at 08:37:26AM -0500, rob pike, esq. wrote:
>
> In any case, it's trivial to change. Just eliminate the variable
> 'top' altogether from the function du() in /sys/src/cmd/du.c. I've
> made the change on our system.
>
No scripts that will break because of the change? Du(1) is used quite
extensively because of find's absence, I'd hate to be the one to
create a problem by trying to be helful :-)
++L
next prev parent reply other threads:[~2002-03-21 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-21 13:37 rob pike, esq.
2002-03-21 13:44 ` Lucio De Re [this message]
2002-03-21 13:47 ` Lucio De Re
2002-03-22 10:21 ` bs
-- strict thread matches above, loose matches on Subject: below --
2002-03-21 7:48 Lucio De Re
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=20020321154427.H9019@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
--cc=rob@plan9.bell-labs.com \
/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).