From: Linus Torvalds <torvalds@linux-foundation.org>
To: Kari Argillander <kari.argillander@stargateuniverse.net>
Cc: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>,
ntfs3@lists.linux.dev, "Theodore Ts'o" <tytso@mit.edu>,
Christoph Hellwig <hch@lst.de>,
Matthew Wilcox <willy@infradead.org>,
Eric Biggers <ebiggers@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
Christian Brauner <christian.brauner@ubuntu.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NTFS3 driver is orphan already. What we do?
Date: Wed, 27 Apr 2022 10:47:17 -0700 [thread overview]
Message-ID: <CAHk-=wihuvzVTozzNLZT=uFzJH6uM7ZNKN7fYVpm0v2KkY6Jxg@mail.gmail.com> (raw)
In-Reply-To: <da20d32b-5185-f40b-48b8-2986922d8b25@stargateuniverse.net>
[ Sad state of affairs mostly edited out ]
On Tue, Apr 26, 2022 at 2:22 AM Kari Argillander
<kari.argillander@stargateuniverse.net> wrote:
>
> I also did suggest that I could co maintain this driver to take burden from
> Konstantin, but haven't got any replay.
If you are willing to maintain it (and maybe find other like-minded
people to help you), I think that would certainly be a thing to try.
And if we can find *nobody* that ends up caring and maintaining, then
I guess we should remove it, rather than end up with *two* effectively
unmaintained copies of NTFS drivers.
Not that two unmaintained filesystems are much worse than one :-p
Linus
next prev parent reply other threads:[~2022-04-27 17:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 9:22 NTFS3 driver is orphan already. What we do? Kari Argillander
2022-04-27 17:47 ` Linus Torvalds [this message]
2022-04-28 0:47 ` Namjae Jeon
2022-04-29 16:45 ` Kari Argillander
2022-04-29 19:59 ` David Sterba
2022-04-28 9:38 ` Leonidas-Panagiotis Papadakos
2022-05-01 17:13 ` Konstantin Komarov
2022-05-02 20:49 ` Kari Argillander
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='CAHk-=wihuvzVTozzNLZT=uFzJH6uM7ZNKN7fYVpm0v2KkY6Jxg@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=almaz.alexandrovich@paragon-software.com \
--cc=christian.brauner@ubuntu.com \
--cc=djwong@kernel.org \
--cc=ebiggers@kernel.org \
--cc=hch@lst.de \
--cc=kari.argillander@stargateuniverse.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs3@lists.linux.dev \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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).