From: Liu Bo <liubo2009@cn.fujitsu.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 2/3] Btrfs-progs: make get default report correctly
Date: Mon, 02 Jul 2012 09:39:45 +0800 [thread overview]
Message-ID: <4FF0FBE1.4000303@cn.fujitsu.com> (raw)
In-Reply-To: <20120629103643.GB1877@zambezi.lan>
On 06/29/2012 06:36 PM, Ilya Dryomov wrote:
> On Fri, Jun 29, 2012 at 06:00:37PM +0800, Liu Bo wrote:
>> We have both set-default and get-default, but actually our get-default
>> does not show which one is the default one.
>>
>> This patch plus the kernel side patch fix this.
>
> Are you referring to the fact that get-default in Chris' btrfs-progs
> master lists all subvolumes instead of showing the default one? If so,
> I fixed that problem a while ago, patch is in Hugo's integration branch.
>
So can you please show me a link about your patch?
thanks,
liubo
> Thanks,
>
> Ilya
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2012-07-02 1:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 10:00 [PATCH 1/3] Btrfs-progs: add support to set subvolume/snapshot readonly Liu Bo
2012-06-29 10:00 ` [PATCH 2/3] Btrfs-progs: make get default report correctly Liu Bo
2012-06-29 10:36 ` Ilya Dryomov
2012-07-02 1:39 ` Liu Bo [this message]
2012-07-02 9:45 ` Ilya Dryomov
2012-07-03 1:27 ` Liu Bo
2012-06-29 10:00 ` [PATCH 3/3] Btrfs-progs: add 's' option for 'btrfs subvolume list' Liu Bo
2012-07-04 15:41 ` David Sterba
2012-07-05 12:42 ` Liu Bo
2012-06-29 10:21 ` [PATCH 1/3] Btrfs-progs: add support to set subvolume/snapshot readonly Ilya Dryomov
2012-07-02 2:07 ` Liu Bo
2012-07-02 10:00 ` Ilya Dryomov
2012-07-03 1:46 ` Liu Bo
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=4FF0FBE1.4000303@cn.fujitsu.com \
--to=liubo2009@cn.fujitsu.com \
--cc=idryomov@gmail.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.