From: Chris Mason <chris.mason@oracle.com>
To: Jeff Mahoney <jeffm@jeffreymahoney.com>
Cc: Btrfs Development List <linux-btrfs@vger.kernel.org>,
Jeff Mahoney <jeffm@suse.com>
Subject: Re: [PATCH] New fs-specific Kconfig options should go in fs/$FS/Kconfig, not fs/Kconfig.
Date: Wed, 04 Feb 2009 13:59:31 -0500 [thread overview]
Message-ID: <1233773971.20318.62.camel@think.oraclecorp.com> (raw)
In-Reply-To: <1233716308-19702-1-git-send-email-jeffm@suse.com>
On Tue, 2009-02-03 at 21:58 -0500, Jeff Mahoney wrote:
> Commit 699b6faa2ab283219914501d5117f8a93c7e441b allowed btrfs ACLs to
> be selectable, but put the option in the main fs/Kconfig, and didn't
> make it depend on btrfs.
>
> This patch moves the option and adds the dependency.
>
FYI, I did merge this but folded it into the original ACL patch. I
rebased the tree because Yan found a bug that could cause corruption
during btrfs-vol -b processing.
So, if you've pulled the unstable tree, you'll want to pull again and
git gc
-chris
prev parent reply other threads:[~2009-02-04 18:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 2:58 [PATCH] New fs-specific Kconfig options should go in fs/$FS/Kconfig, not fs/Kconfig Jeff Mahoney
2009-02-04 18:59 ` Chris Mason [this message]
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=1233773971.20318.62.camel@think.oraclecorp.com \
--to=chris.mason@oracle.com \
--cc=jeffm@jeffreymahoney.com \
--cc=jeffm@suse.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