From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Yangtao Li <frank.li@vivo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: mark ecryptfs as orphan state
Date: Tue, 21 Mar 2023 07:35:59 +0100 [thread overview]
Message-ID: <ZBlQT2Os/hB2Rxqh@kroah.com> (raw)
In-Reply-To: <20230320182103.46350-1-frank.li@vivo.com>
On Tue, Mar 21, 2023 at 02:21:03AM +0800, Yangtao Li wrote:
> ecryptfs has been inactive for a long time, and in fact the filesystem
> has no active maintainers. I sent a patch last August, no response
> till now. Let's mark it as Orphan status.
>
> Maybe in 2025 we can remove this unmaintained file system?
>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Why send this to me?
> Signed-off-by: Yangtao Li <frank.li@vivo.com>
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 541e7dc05f48..4a6236d5a6ce 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7270,7 +7270,7 @@ F: drivers/media/dvb-frontends/ec100*
> ECRYPT FILE SYSTEM
> M: Tyler Hicks <code@tyhicks.com>
> L: ecryptfs@vger.kernel.org
> -S: Odd Fixes
> +S: Orphan
Why not also cc: the two email addresses here? And if this is really
orphaned, then remove them as well, right?
> W: http://ecryptfs.org
> W: https://launchpad.net/ecryptfs
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/tyhicks/ecryptfs.git
These all too need to go if this really is orphaned code. But first,
try sending it to the right people (like the linux-fs mailing list as
well?)
thanks,
greg k-h
next prev parent reply other threads:[~2023-03-21 6:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-20 18:21 [PATCH] MAINTAINERS: mark ecryptfs as orphan state Yangtao Li
2023-03-21 6:35 ` Greg Kroah-Hartman [this message]
2023-03-22 17:18 ` Yangtao Li
2023-03-22 17:19 ` Yangtao Li
2023-03-24 22:42 ` Tyler Hicks
2023-04-03 12:44 ` Christian Brauner
2023-04-03 13:44 ` Yangtao Li
2023-04-04 2:57 ` Tyler Hicks (Microsoft)
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=ZBlQT2Os/hB2Rxqh@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=frank.li@vivo.com \
--cc=linux-kernel@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