[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKYAXd8q=TLxOZi5qB8Xinq+-ErtPwwF13HOsw2JA4P-sx6kNw@mail.gmail.com>
Date: Fri, 28 Nov 2025 08:19:09 +0900
From: Namjae Jeon <linkinjeon@...nel.org>
To: Matthew Wilcox <willy@...radead.org>
Cc: Amir Goldstein <amir73il@...il.com>, viro@...iv.linux.org.uk, brauner@...nel.org,
hch@...radead.org, hch@....de, tytso@....edu, jack@...e.cz, djwong@...nel.org,
josef@...icpanda.com, sandeen@...deen.net, rgoldwyn@...e.com,
xiang@...nel.org, dsterba@...e.com, pali@...nel.org, ebiggers@...nel.org,
neil@...wn.name, linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
iamjoonsoo.kim@....com, cheol.lee@....com, jay.sim@....com, gunho.lee@....com
Subject: Re: [PATCH v2 00/11] ntfsplus: ntfs filesystem remake
On Thu, Nov 27, 2025 at 11:58 PM Matthew Wilcox <willy@...radead.org> wrote:
>
> On Thu, Nov 27, 2025 at 09:17:54PM +0900, Namjae Jeon wrote:
> > > Why is the rebranding to ntfsplus useful then?
> > >
> > > I can understand that you want a new name for a new ntfsprogs-plus project
> > > which is a fork of ntfs-3g, but I don't think that the new name for the kernel
> > > driver is useful or welcome.
> > Right, I wanted to rebrand ntfsprogs-plus and ntfsplus into a paired
> > set of names. Also, ntfs3 was already used as an alias for ntfs, so I
> > couldn't touch ntfs3 driver without consensus from the fs maintainers.
>
> I think you're adding more confusion than you're removing with the name
> change. Please, just call it ntfs. We have hfs and hfsplus already,
> and those refer to different filesystems. We should just call this ntfs.
Okay, I will change it back to the name "ntfs" in the next version.
Thanks!
Powered by blists - more mailing lists