From: Al Viro <viro@zeniv.linux.org.uk>
To: Jan Kara <jack@suse.cz>
Cc: Cedric Blancher <cedric.blancher@gmail.com>,
"Darrick J. Wong" <djwong@kernel.org>,
Jeff Layton <jlayton@kernel.org>,
linux-fsdevel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH] sysv: Remove the filesystem
Date: Tue, 7 Jan 2025 15:13:10 +0000 [thread overview]
Message-ID: <20250107151310.GO1977892@ZenIV> (raw)
In-Reply-To: <dl55ihsxe45c7bv2g7w7hlqugs3wdwebfpuanzcxe4qsvm5uzt@dzafyykaaeyj>
On Tue, Jan 07, 2025 at 11:08:13AM +0100, Jan Kara wrote:
> > Better add a test to CI
>
> That's easier said than done. AFAIK we don't have tools to create the
> filesystem or verify its integrity. And perhaps most importantly I don't
> know of anyone wishing to invest their time into keeping this filesystem
> alive. Are you volunteering to become a SYSV maintainer?
To be fair, it's very close to minixfs, so the burden wouldn't be all
that awful - just need to keep changes in sync, mostly.
That, however, presumes an actual mind - AI and CI won't cut it.
next prev parent reply other threads:[~2025-01-07 15:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 16:24 [PATCH] sysv: Remove the filesystem Jan Kara
2025-01-06 19:52 ` Jeff Layton
2025-01-06 23:31 ` Darrick J. Wong
2025-01-07 7:17 ` Cedric Blancher
2025-01-07 10:08 ` Jan Kara
2025-01-07 15:13 ` Al Viro [this message]
2025-01-06 20:41 ` Matthew Wilcox
2025-01-07 14:35 ` Christian Brauner
2025-01-08 22:32 ` Bill O'Donnell
2025-01-09 15:05 ` Christian Brauner
2025-01-09 23:08 ` Bill O'Donnell
-- strict thread matches above, loose matches on Subject: below --
2025-02-20 16:39 Jan Kara
2025-02-20 18:50 ` Darrick J. Wong
2025-02-20 20:06 ` Jeff Layton
2025-02-21 9:38 ` Christian Brauner
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=20250107151310.GO1977892@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=brauner@kernel.org \
--cc=cedric.blancher@gmail.com \
--cc=djwong@kernel.org \
--cc=jack@suse.cz \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.