From: Linus Torvalds <torvalds@linux-foundation.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs updates for 2.6.29-rc
Date: Sat, 7 Feb 2009 08:37:51 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0902070837350.3048@localhost.localdomain> (raw)
In-Reply-To: <1233965457.10366.11.camel@think.oraclecorp.com>
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
which is all fine, but last I saw some (most?) distributions use POSIX
ACL's for things like desktop access permissions to /dev/audio etc.
I don't particularly have to like it, but it does mean that if you don't
do POSIX ACL's, and have btrfs as your root filesystem, you'll quite
likely not get sound when logging in.
I dunno. I haven't actually yet tried to convert my laptop, so I just
reacted to this thanks to the new question..
Linus
next prev parent reply other threads:[~2009-02-07 16:38 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 [this message]
2009-02-07 23:50 ` Chris Mason
2009-02-08 10:16 ` Kay Sievers
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=alpine.LFD.2.00.0902070837350.3048@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=chris.mason@oracle.com \
--cc=linux-kernel@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).