ntfs3.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Konstantin Komarov <almaz.alexandrovich@paragon-software.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
	Kari Argillander <kari.argillander@stargateuniverse.net>
Cc: "ntfs3@lists.linux.dev" <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: Sun, 1 May 2022 17:13:39 +0000	[thread overview]
Message-ID: <0f48e2eb2b0740b1b85e3b8d910c4bd8@paragon-software.com> (raw)
In-Reply-To: <CAHk-=wihuvzVTozzNLZT=uFzJH6uM7ZNKN7fYVpm0v2KkY6Jxg@mail.gmail.com>

> From: Linus Torvalds <torvalds@linux-foundation.org>
> Sent: Wednesday, April 27, 2022 7:47 PM
> 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?
> [ 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

Hello Linus, Kari and all.

First and foremost I need to state that active work on NTFS3 driver has never stopped,
and it was never decided to "orphan" NTFS3.  Currently we are still in the middle of the process
of getting the Kernel.org account. We need to sign our PGP key to move forward, but
the process is not so clear (will be grateful to get some process desciption), so it is going quite slow
trying to unravel the topic.

As for now, we can prepare patches/pull requests through the github, 
and submit them right now (we have quite a bunch of fixes
for new Kernels support, bugfixes and fstests fixes) -- if Linus approves this approach
until we set up the proper git.kernel.org repo.

Also, to clarify this explicitly: in addition to the driver, we're working of ntfs3 utilities as well.

Overall, nevertheless the NTFS3 development pace has been slowed down a bit for previous couple
of months, its state is still the same as before: it is fully maintained and being developed.

And finally, we apologize for late reply; I allowed me short vacation after most restrictions because
of covid ended up this month in Germany.


  parent reply	other threads:[~2022-05-01 17:23 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
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 [this message]
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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0f48e2eb2b0740b1b85e3b8d910c4bd8@paragon-software.com \
    --to=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=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \


* 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).