From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: Eric Biggers <ebiggers@kernel.org>
Cc: Guenter Roeck <linux@roeck-us.net>,
Chandan Rajendra <chandan@linux.vnet.ibm.com>,
<linux-ext4@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [f2fs-dev] [PATCH] fscrypt: remove filesystem specific build config option
Date: Thu, 24 Jan 2019 00:03:37 -0500 [thread overview]
Message-ID: <20190124050337.GD8785@mit.edu> (raw)
In-Reply-To: <20190111010116.GG149637@gmail.com>
On Thu, Jan 10, 2019 at 05:01:17PM -0800, Eric Biggers wrote:
>
> Indeed, Chandan Rajendra sent out a new version of the patch which fixes the
> problem (by removing the 'select BLOCK' from fs/ubifs/Kconfig), but it never
> made it into the fscrypt tree and hence never made it into linux-next.
>
> Ted, what you are planning to do with the fscrypt tree following the fsverity
> discussion? IMO, we should keep the fsverity stuff in its own branch, separate
> from any fscrypt changes. As a suggestion, in the branch "fscrypt" of my
> linux.git repo [1], I applied just these four patches on top of v5.0-rc1 and
> resolved the conflicts with them no longer being on top of fsverity...
Sorry, I was on vacation last week and I've been catching up on things
this week. I've reset the master branch on my fscrypt.git tree so
that it has what you have on your fscrypt branch, rebased to 5.0-rc3.
Also, as we had talked about earlier, it probably makes sense to set
up jointly maintained git tree for fscrypt and fsverity. My proposal
is that we set up a new fscrypt.git tree, at
/pub/scm/fs/fscrypt/fscrypt.git, that would be owned by the "FSCRYPT
group", with group membership being ebiggers, jaeguk, and tytso.
We'll have to figure out ways that we can jointly update the git tree
without stepping on each other, probably using a group chat. Does
that sound good to you?
- Ted
next prev parent reply other threads:[~2019-01-24 5:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 23:32 [PATCH] fscrypt: remove filesystem specific build config option Guenter Roeck
2019-01-11 1:01 ` [f2fs-dev] " Eric Biggers
2019-01-24 5:03 ` Theodore Y. Ts'o [this message]
2019-01-24 18:29 ` Eric Biggers
2019-01-24 21:22 ` Theodore Y. Ts'o
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=20190124050337.GD8785@mit.edu \
--to=tytso@mit.edu \
--cc=chandan@linux.vnet.ibm.com \
--cc=ebiggers@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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).