linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH v2 0/2] btrfs-progs: completion: Small fixes to make debug simpler
Date: Mon, 13 Aug 2018 14:02:42 +0800	[thread overview]
Message-ID: <20180813060244.8795-1-wqu@suse.com> (raw)

For developer, it's pretty common to use "btrfs check" or "btrfs ins
dump-tree" on raw dumps.
Even for end user, they may hit case where they need to run "btrfs check"
on raw images.

However "btrfs check" can only complete real block devices, and
"btrfs inspect dump-tree" can only complete dir.

Make them to use _filedir() so any filename can be completed and save us
developer a little time and nerve hitting that holy tab.

changelog:
v2:
  Discard _btrfs_dev() macro completely.

Qu Wenruo (2):
  btrfs-progs: completion: Use _filedir() to replace _btrfs_devs()
  btrfs-progs: completion: Let dump-tree/dump-super/inode-resolve to
    accept any file

 btrfs-completion | 19 ++++++-------------
 1 file changed, 6 insertions(+), 13 deletions(-)

-- 
2.18.0

             reply	other threads:[~2018-08-13  8:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-13  6:02 Qu Wenruo [this message]
2018-08-13  6:02 ` [PATCH v2 1/2] btrfs-progs: completion: Use _filedir() to replace _btrfs_devs() Qu Wenruo
2018-08-13  6:02 ` [PATCH v2 2/2] btrfs-progs: completion: Let dump-tree/dump-super/inode-resolve to accept any file Qu Wenruo
2018-08-20 13:40 ` [PATCH v2 0/2] btrfs-progs: completion: Small fixes to make debug simpler David Sterba

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=20180813060244.8795-1-wqu@suse.com \
    --to=wqu@suse.com \
    --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).