From: Theodore Ts'o <tytso@mit.edu>
To: Phillip Susi <psusi@ubuntu.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] mke2fs: clarify inode ratio in man page
Date: Tue, 15 Oct 2013 23:38:47 -0400 [thread overview]
Message-ID: <20131016033847.GF28823@thunk.org> (raw)
In-Reply-To: <1381156782-31422-1-git-send-email-psusi@ubuntu.com>
On Mon, Oct 07, 2013 at 10:39:42AM -0400, Phillip Susi wrote:
> The man page still said it was not possible to change the number
> of inodes on a filesystem after creating it. You actually can
> by resizing the fs, so clarify this language a bit.
You didn't include a signed-off-by, but this was a simple enough
documentation-only change that I've used by discretion to accept it.
Cheers,
- Ted
next prev parent reply other threads:[~2013-10-16 3:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 14:39 [PATCH] mke2fs: clarify inode ratio in man page Phillip Susi
2013-10-16 3:38 ` Theodore Ts'o [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-25 15:53 Phillip Susi
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=20131016033847.GF28823@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=psusi@ubuntu.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).