linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: "Viacheslav Dubeyko" <slava@dubeyko.com>,
	"Christoph Hellwig" <hch@infradead.org>,
	"Ernesto A. Fernández" <ernesto.mnd.fernandez@gmail.com>,
	linux-fsdevel@vger.kernel.org,
	"Andreas Gruenbacher" <agruenba@redhat.com>,
	"Alexander Viro" <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH 2/2] hfsplus: add mount option to enable ACL support
Date: Tue, 17 Oct 2017 01:03:07 -0700	[thread overview]
Message-ID: <20171017080307.GB27649@infradead.org> (raw)
In-Reply-To: <20171017075346.GM9762@quack2.suse.cz>

On Tue, Oct 17, 2017 at 09:53:46AM +0200, Jan Kara wrote:
> With xattr support the situation is different. It has been broken for four
> years and nobody complained. That is a good indication nobody uses that
> code and we can drop it. Furthermore, Christoph pointed out that original
> HFS+ in MacOS never supported xattrs which makes it even less likely that
> someone uses that functionality (as you cannot use it if you want your
> filesystem to stay compatible with MacOS).

s/xattrs/Posix ACLs/g

  reply	other threads:[~2017-10-17  8:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27  3:10 [PATCH 1/2] hfsplus: preserve i_mode if __hfsplus_set_posix_acl() fails Ernesto A. Fernández
2017-07-27  3:13 ` [PATCH 2/2] hfsplus: add mount option to enable ACL support Ernesto A. Fernández
2017-07-27  9:41   ` Jan Kara
2017-07-27  9:50     ` Christoph Hellwig
2017-10-14  2:43       ` Ernesto A. Fernández
2017-10-16  7:42         ` Christoph Hellwig
2017-10-16 15:50           ` Viacheslav Dubeyko
2017-10-17  7:53             ` Jan Kara
2017-10-17  8:03               ` Christoph Hellwig [this message]
2017-10-17 15:20                 ` Viacheslav Dubeyko
2017-07-27 21:29     ` Ernesto A. Fernández
2017-07-27  9:18 ` [PATCH 1/2] hfsplus: preserve i_mode if __hfsplus_set_posix_acl() fails Jan Kara

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=20171017080307.GB27649@infradead.org \
    --to=hch@infradead.org \
    --cc=agruenba@redhat.com \
    --cc=ernesto.mnd.fernandez@gmail.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=slava@dubeyko.com \
    --cc=viro@zeniv.linux.org.uk \
    /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).