From: Chris Mason <chris.mason@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs updates for 2.6.29-rc
Date: Sat, 07 Feb 2009 18:50:01 -0500 [thread overview]
Message-ID: <1234050601.19599.13.camel@think.oraclecorp.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0902070837350.3048@localhost.localdomain>
On Sat, 2009-02-07 at 08:37 -0800, Linus Torvalds wrote:
> On Fri, 6 Feb 2009, Chris Mason wrote:
> >
> > Crud, the confusion would be me. I missed the cleanups and bug fixes
> > between 2.6.29-rc1 and rc3. The correct diffstat and short log are
> > below, and the only non-btrfs change is to the MAINTAINERS file.
>
> Ok.
>
> I notice that it now asks about ACL's, and says
>
> If you don't know what Access Control Lists are, say N
The text was stolen from ext3, or from someone else that stole it from
ext3....it made sense to me to stay consistent with the others here.
The config option really just provides a way to enable
CONFIG_FS_POSIX_ACL.
The btrfs code only looks for CONFIG_FS_POSIX_ACL, and doesn't have a
special mount -o acl,xattr,security.
-chris
next prev parent reply other threads:[~2009-02-07 23:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 16:22 [GIT PULL] Btrfs updates for 2.6.29-rc Chris Mason
2009-02-06 16:53 ` Linus Torvalds
2009-02-06 21:51 ` Chris Mason
2009-02-06 21:59 ` Linus Torvalds
2009-02-07 0:10 ` Chris Mason
2009-02-07 16:37 ` Linus Torvalds
2009-02-07 23:50 ` Chris Mason [this message]
2009-02-08 10:16 ` Kay Sievers
-- strict thread matches above, loose matches on Subject: below --
2009-02-13 20:25 Chris Mason
2009-02-26 15:09 Chris Mason
2009-02-26 15:11 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=1234050601.19599.13.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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