From: Gabriel Krisman Bertazi <krisman@collabora.com>
To: Jan Kara <jack@suse.cz>
Cc: Matthew Bobrowski <repnop@google.com>,
Amir Goldstein <amir73il@gmail.com>,
linux-man@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>
Subject: Re: [PATCH v4] fanotify.7, fanotify_mark.2: Document FAN_FS_ERROR
Date: Mon, 18 Apr 2022 12:37:04 -0400 [thread overview]
Message-ID: <87sfqabb67.fsf@collabora.com> (raw)
In-Reply-To: <20220413082751.57lzlgwiursy7onk@quack3.lan> (Jan Kara's message of "Wed, 13 Apr 2022 10:27:51 +0200")
Jan Kara <jack@suse.cz> writes:
> On Tue 12-04-22 14:50:28, Gabriel Krisman Bertazi wrote:
> BTW any plans to add support to XFS or btrfs? I guess it would be good to
> spread the use a bit more so that it does not end up as a niche ext4
> feature not very useful to programmers...
Hi Jan,
Yes. i have plans to wire other filesystems, starting with btrfs, but I
have a few items ahead of it. I definitely don't want to have this as a
single-filesystem feature.
> Otherwise the changes look good (modulo some language issues Matthew
> already pointed out).
Thanks. I'm following up with the v5 shortly.
--
Gabriel Krisman Bertazi
prev parent reply other threads:[~2022-04-18 16:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <YlDCh1OEVxSgu2L9@google.com>
[not found] ` <CAOQ4uxjpwZs8Jg-cZ5yWqUis=FA=+g+ycjdBchz0kzKBhs6HxQ@mail.gmail.com>
[not found] ` <YlSzOaBTLA+LqOhU@google.com>
[not found] ` <87bkx7xj3q.fsf@collabora.com>
[not found] ` <YlTKQWTwWY45g9Ws@google.com>
2022-04-12 18:50 ` [PATCH v4] fanotify.7, fanotify_mark.2: Document FAN_FS_ERROR Gabriel Krisman Bertazi
2022-04-12 23:14 ` Matthew Bobrowski
2022-04-18 16:35 ` Gabriel Krisman Bertazi
2022-04-13 8:27 ` Jan Kara
2022-04-13 10:38 ` Amir Goldstein
2022-04-18 16:37 ` Gabriel Krisman Bertazi [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=87sfqabb67.fsf@collabora.com \
--to=krisman@collabora.com \
--cc=amir73il@gmail.com \
--cc=jack@suse.cz \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=repnop@google.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.