From: Chris Mason <chris.mason@oracle.com>
To: David Bruzos <David.Bruzos@jaxport.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Optionally enforced time-based ACLs for BTRFS
Date: Fri, 27 Apr 2012 10:57:08 -0400 [thread overview]
Message-ID: <20120427145708.GG7340@shiny> (raw)
In-Reply-To: <DE6EA944EF16AF4CA4C0D1856C83808006C7F05ECB@ex7>
On Thu, Apr 26, 2012 at 05:27:12PM -0400, David Bruzos wrote:
> Hi Chris:
> Thank you for your very informative response. I will post the message to linux-fsdevel and see what they have to say about it.
>
> Any comments you would like to share regarding why something like what I suggested has apparently never been implemented?
Most features in the kernel are based on customer demand. I think we
just haven't had enough people asking for it ;)
-chris
prev parent reply other threads:[~2012-04-27 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 19:30 Optionally enforced time-based ACLs for BTRFS David Bruzos
2012-04-26 20:04 ` Chris Mason
2012-04-26 21:27 ` David Bruzos
2012-04-27 14:57 ` 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=20120427145708.GG7340@shiny \
--to=chris.mason@oracle.com \
--cc=David.Bruzos@jaxport.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).