From: Josef Bacik <josef@redhat.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [GIT PULL] ENOSPC rework and random fixes for next merge window
Date: Tue, 27 Sep 2011 11:11:56 -0400 [thread overview]
Message-ID: <4E81E7BC.40006@redhat.com> (raw)
In-Reply-To: <20110927150117.GF22205@twin.jikos.cz>
On 09/27/2011 11:01 AM, David Sterba wrote:
> On Mon, Sep 26, 2011 at 05:36:32PM -0400, Josef Bacik wrote:
>> Btrfs: fix how we mount subvol=<whatever>
>
> this patch was not sent to the mailiglist, although this is an
> intersting change from the user's POV:
>
> subvolumes are now mountable via
>
> -o subvol=any/path/always/relative/to/toplevel
>
> which makes subvolrootid obsolete and fixes the mess with set-default
> and subvol= mounts.
>
Oops crap sorry I thought I had sent it to the list already, my bad.
Thanks,
Josef
next prev parent reply other threads:[~2011-09-27 15:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-26 21:36 [GIT PULL] ENOSPC rework and random fixes for next merge window Josef Bacik
2011-09-27 15:01 ` David Sterba
2011-09-27 15:11 ` Josef Bacik [this message]
2011-09-28 11:58 ` Chris Mason
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=4E81E7BC.40006@redhat.com \
--to=josef@redhat.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).