linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: "Jean-Pierre André" <jean-pierre.andre@wanadoo.fr>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	ntfs-3g-devel <ntfs-3g-devel@lists.sourceforge.net>,
	ntfs-3g-news <ntfs-3g-news@lists.sourceforge.net>
Subject: Re: Stable NTFS-3G + NTFSPROGS 2021.8.22 Released
Date: Mon, 30 Aug 2021 20:09:38 +0100	[thread overview]
Message-ID: <YS0s8oEjE6gRN6XT@casper.infradead.org> (raw)
In-Reply-To: <d343b1d7-6587-06a5-4b60-e4c59a585498@wanadoo.fr>

On Mon, Aug 30, 2021 at 07:59:17PM +0200, Jean-Pierre André wrote:
> The NTFS-3G project globally aims at providing a stable NTFS driver. The
> project's advanced branch has specifically aimed at developing, maturing,
> and releasing features for user feedback prior to feature integration into
> the project's main branch.

So do I understand correctly ...

 - We have an NTFS filesystem from Anton Altaparmakov in fs/ntfs which was
   merged in 1997 and is read only.
 - We have Paragon's NTFS3 in the process of being merged
 - We have Tuxera's NTFS-3G hosted externally on Github that uses FUSE

Any other implementations of NTFS for Linux that we should know about?
Is there any chance that the various developers involved can agree to
cooperate on a single implementation?

  reply	other threads:[~2021-08-30 19:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 17:59 Stable NTFS-3G + NTFSPROGS 2021.8.22 Released Jean-Pierre André
2021-08-30 19:09 ` Matthew Wilcox [this message]
2021-09-02  8:58   ` 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=YS0s8oEjE6gRN6XT@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=jean-pierre.andre@wanadoo.fr \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=ntfs-3g-devel@lists.sourceforge.net \
    --cc=ntfs-3g-news@lists.sourceforge.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).