From: "Lakshmipathi.G" <lakshmipathi.g@giis.co.in>
To: Su Yue <suy.fnst@cn.fujitsu.com>
Cc: Lakshmipathi.Ganapathi@collabora.co.uk,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] v2: btrfs-progs: Introduce 'btrfs inspect-internal dump-csum' option
Date: Mon, 16 Jul 2018 16:00:46 +0530 [thread overview]
Message-ID: <20180716103046.GA20821@giis.co.in> (raw)
In-Reply-To: <9b443693-3219-5f62-8a79-aa3c67f93c20@cn.fujitsu.com>
> >Sample usage:
> >btrfs inspect-internal dump-csum /btrfs/50gbfile /dev/sda4
> I'm not like the way to pass a filename as a argument.
> Just print content to stdout, let users decides where to redirect.
> And it will decrease amount of codes(part of checking and opening files).
>
Ok, will remove default output file creation part (filename.csumdump) and
print the content to stdout.
Cheers.
Lakshmipathi.G
next parent reply other threads:[~2018-07-16 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <612cc1b7-1593-478e-ff9f-21784d387a96@cn.fujitsu.com>
[not found] ` <9b443693-3219-5f62-8a79-aa3c67f93c20@cn.fujitsu.com>
2018-07-16 10:30 ` Lakshmipathi.G [this message]
2018-07-16 3:16 [PATCH] v2: btrfs-progs: Introduce 'btrfs inspect-internal dump-csum' option Lakshmipathi.G
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=20180716103046.GA20821@giis.co.in \
--to=lakshmipathi.g@giis.co.in \
--cc=Lakshmipathi.Ganapathi@collabora.co.uk \
--cc=linux-btrfs@vger.kernel.org \
--cc=suy.fnst@cn.fujitsu.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).