From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] man du -s correction diff
Date: Tue, 02 Nov 2021 12:57:15 -0400 [thread overview]
Message-ID: <4EBE77893E9CE3937BDC099792A210A9@eigenstate.org> (raw)
In-Reply-To: <YYFf3ZL7UOzALlPa@beryllium.local>
Quoth Humm <hummsmith42@gmail.com>:
> Quoth Kyle Milz:
> >the description in the manual for du -s looks just plain wrong.
> >by itself du -s only prints values for the top level.
>
> The top level being each `file` argument, and the values being gotten
> by descending the hierarchy as always.
>
> --
> Humm
>
I agree that the current phrasing is a bit confusing.
What about "for each file" => "for each argument"?
next prev parent reply other threads:[~2021-11-02 19:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 22:46 Kyle Milz
2021-11-01 23:39 ` umbraticus
2021-11-02 16:49 ` Kyle Milz
2021-11-02 4:25 ` Xiao-Yong Jin
2021-11-02 9:30 ` hiro
2021-11-02 10:42 ` Eckard Brauer
2021-11-02 15:57 ` Humm
2021-11-02 16:57 ` ori [this message]
2021-11-02 18:54 ` Kyle Milz
2021-11-02 18:54 ` Eckard Brauer
2021-11-02 19:38 ` ori
2021-11-02 21:53 ` Kyle Milz
2021-11-02 19:22 ` hiro
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=4EBE77893E9CE3937BDC099792A210A9@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
/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).