From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 5/5] btrfs-progs: Doc/mkfs: Add explanation for rootdir parameter
Date: Mon, 4 Sep 2017 10:47:19 +0000 (UTC) [thread overview]
Message-ID: <pan$d6ecf$22d097ca$4cb2dd48$57a81ef5@cox.net> (raw)
In-Reply-To: 20170904064110.25951-6-quwenruo.btrfs@gmx.com
Qu Wenruo posted on Mon, 04 Sep 2017 15:41:10 +0900 as excerpted:
> +NOTE: Result btrfs will be shrink to it minimal size, exceeding space will not
> +be accessible unless resized.
s/exceeding/additional/
(Exceeding could be used if reworded, but the results I came up with were
much less concise than the above with the single substitution, so...)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2017-09-04 10:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 6:41 [PATCH 0/5] Mkfs: Rework --rootdir to a more generic behavior Qu Wenruo
2017-09-04 6:41 ` [PATCH 1/5] btrfs-progs: Fix one-byte overlap bug in free_block_group_cache Qu Wenruo
2017-09-04 6:41 ` [PATCH 2/5] btrfs-progs: mkfs: Rework rootdir option to avoid custom chunk layout Qu Wenruo
2017-09-04 6:41 ` [PATCH 3/5] btrfs-progs: mkfs: Shrink the image for rootdir to minimal size Qu Wenruo
2017-09-04 6:41 ` [PATCH 4/5] btrfs-progs: mkfs: Update allocation info before verbose output Qu Wenruo
2017-09-04 6:41 ` [PATCH 5/5] btrfs-progs: Doc/mkfs: Add explanation for rootdir parameter Qu Wenruo
2017-09-04 10:47 ` Duncan [this message]
2017-09-04 18:08 ` [PATCH 0/5] Mkfs: Rework --rootdir to a more generic behavior David Sterba
2017-09-05 8:19 ` Qu Wenruo
2017-09-05 19:05 ` Goffredo Baroncelli
2017-09-06 3:20 ` Qu Wenruo
2017-09-06 18:44 ` Goffredo Baroncelli
2017-09-06 11:31 ` Austin S. Hemmelgarn
2017-09-06 16:43 ` Goffredo Baroncelli
2017-09-06 17:16 ` Austin S. Hemmelgarn
2017-09-06 17:48 ` Goffredo Baroncelli
2017-09-06 18:02 ` Austin S. Hemmelgarn
2017-09-06 18:31 ` Goffredo Baroncelli
2017-09-06 18:46 ` Austin S. Hemmelgarn
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='pan$d6ecf$22d097ca$4cb2dd48$57a81ef5@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.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).