From: "Lakshmipathi.G" <lakshmipathi.g@giis.co.in>
To: dsterba@suse.cz, Qu Wenruo <quwenruo@cn.fujitsu.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btfs-progs: fsck-tests: corrupt nlink value test
Date: Thu, 26 Jan 2017 01:13:15 +0530 [thread overview]
Message-ID: <20170125194314.GA10888@giis.co.in> (raw)
In-Reply-To: <20170117151506.GS12081@twin.jikos.cz>
> Both approaches have their pros and cons so I'll accept both. The
> functionality provided by the corrupt block utility can be used, any
> changes to the command line UI will be also applied to the test scripts.
okay, I'll continue mixing both approaches.
prev parent reply other threads:[~2017-01-25 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 23:19 [PATCH] btfs-progs: fsck-tests: corrupt nlink value test Lakshmipathi.G
[not found] ` <c9e21f30-2231-94cd-09ed-8422951e7b69@cn.fujitsu.com>
2017-01-10 17:36 ` lakshmipathi.g
2017-01-12 1:19 ` Qu Wenruo
2017-01-12 14:37 ` lakshmipathi.g
2017-01-13 1:14 ` Qu Wenruo
2017-01-16 16:35 ` lakshmipathi.g
2017-01-17 15:15 ` David Sterba
2017-01-25 19:43 ` Lakshmipathi.G [this message]
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=20170125194314.GA10888@giis.co.in \
--to=lakshmipathi.g@giis.co.in \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo@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).