From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] make 'btrfs fi show /mnt/point/' works with ending '/' character
Date: Wed, 12 Feb 2014 10:18:26 +0800 [thread overview]
Message-ID: <52FAD9F2.6090001@cn.fujitsu.com> (raw)
In-Reply-To: <1392017310-19951-1-git-send-email-quwenruo@cn.fujitsu.com>
Please ignore this patchset since adding a new option to find_mount_root
is not the best method to
solve the problem.
I'll send a better version patch to fix it.
Thanks
Qu
On mon, 10 Feb 2014 15:28:27 +0800, Qu Wenruo wrote:
> Before this patchset, 'btrfs fi show' can work with '/mnt/point' but not '/mnt/point/',
> which is very annoying since tab completion will add '/' to a directory.
>
> This patchset just reuse the find_mount_root function with some small modification to
> ignore the last '/' only when needed.
>
> Qu Wenruo (3):
> btrfs-progs: move find_mount_root to utils.[ch]
> btrfs-progs: Add path_is_mp option for find_mount_root.
> btrfs-progs: reuse find_mount_root to determine arg type and so on.
>
> cmds-filesystem.c | 7 +++++
> cmds-receive.c | 2 +-
> cmds-send.c | 53 ++-------------------------------
> cmds-subvolume.c | 2 +-
> commands.h | 1 -
> utils.c | 88 +++++++++++++++++++++++++++++++++++++++++++++----------
> utils.h | 1 +
> 7 files changed, 86 insertions(+), 68 deletions(-)
>
next prev parent reply other threads:[~2014-02-12 2:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 7:28 [PATCH 0/3] make 'btrfs fi show /mnt/point/' works with ending '/' character Qu Wenruo
2014-02-10 7:28 ` [PATCH 1/3] btrfs-progs: move find_mount_root to utils.[ch] Qu Wenruo
2014-02-10 7:28 ` [PATCH 2/3] btrfs-progs: Add path_is_mp option for find_mount_root Qu Wenruo
2014-02-10 7:28 ` [PATCH 3/3] btrfs-progs: reuse find_mount_root to determine arg type and so on Qu Wenruo
2014-02-12 2:18 ` Qu Wenruo [this message]
2014-02-12 14:31 ` [PATCH 0/3] make 'btrfs fi show /mnt/point/' works with ending '/' character 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=52FAD9F2.6090001@cn.fujitsu.com \
--to=quwenruo@cn.fujitsu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.