From: Ted Ts'o <tytso@mit.edu>
To: Yongqiang Yang <xiaoqiangnk@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 1/2] dumpe2fs: dump blocks count used by super and GDT
Date: Sat, 19 Nov 2011 23:43:10 -0500 [thread overview]
Message-ID: <20111120044310.GJ4130@thunk.org> (raw)
In-Reply-To: <1321405328-5298-1-git-send-email-xiaoqiangnk@gmail.com>
On Wed, Nov 16, 2011 at 09:02:07AM +0800, Yongqiang Yang wrote:
> Blocks count used by super and GDT is dumped so that users
> can know how many blocks are taken up by super and GDT.
>
> Signed-off-by: Yongqiang Yang <xiaoqiangnk@gmail.com>
I'm not convinced this is sufficiently useful to be worth adding to
dumpe2fs. How many users really need to know this?
- Ted
next prev parent reply other threads:[~2011-11-20 4:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-16 1:02 [PATCH 1/2] dumpe2fs: dump blocks count used by super and GDT Yongqiang Yang
2011-11-16 1:02 ` [PATCH 2/2] libext2fs: remove useless code in ext2fs_super_and_bgd_loc2 Yongqiang Yang
2011-11-20 4:43 ` Ted Ts'o [this message]
2011-11-20 7:08 ` [PATCH 1/2] dumpe2fs: dump blocks count used by super and GDT Yongqiang Yang
2011-11-20 18:28 ` Ted Ts'o
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=20111120044310.GJ4130@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=xiaoqiangnk@gmail.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