From: Al Viro <viro@ZenIV.linux.org.uk>
To: Vito Caputo <vcaputo@pengaru.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
reiserfs-devel@vger.kernel.org
Subject: Re: Reiser4 Linux 4.17.19-1 hangs in Google cloud VM, too.
Date: Tue, 23 Oct 2018 05:14:18 +0100 [thread overview]
Message-ID: <20181023041418.GU32577@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20181023040418.iz7gcph3qha4bkab@shells.gnugeneration.com>
On Mon, Oct 22, 2018 at 09:04:18PM -0700, Vito Caputo wrote:
> > reiser4 has never been in-tree to start with. And name is completely irrelevant -
> > all I'm refering to is that I have not seen any postings on l-k/fsdevel/etc.
> > from anybody working on that particular out-of-tree codebase.
> >
> > Put it that way - I would expect the bitrot from (apparent) decade-long
> > inactivity to be a much more serious problem than anything naming-related.
>
> Would you say bitrot is more or less likely if a project doesn't attract
> fresh meat?
I would say that by now it seems to be a purely academical question - after a while
the bitrot itself is more than enough. If it's maintained by somebody, take that
question to those somebodies, whoever they are. I hadn't seen any indications that
it is, and that's literally all I'm trying to comment upon - *IF* it's been
unmaintained, it's almost certainly far past the point of no return due to bitrot.
next prev parent reply other threads:[~2018-10-23 4:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 10:19 Reiser4 Linux 4.17.19-1 hangs in Google cloud VM, too Metztli Information Technology
2018-10-22 10:19 ` Metztli Information Technology
2018-10-23 3:38 ` Al Viro
2018-10-23 3:47 ` Vito Caputo
2018-10-23 3:54 ` Al Viro
2018-10-23 4:04 ` Vito Caputo
2018-10-23 4:14 ` Al Viro [this message]
2018-10-23 4:28 ` Jose R R
2018-10-23 6:06 ` Edward Shishkin
-- strict thread matches above, loose matches on Subject: below --
2019-01-29 13:54 Metztli Information Technology
2019-01-29 13:54 ` Metztli Information Technology
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=20181023041418.GU32577@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=vcaputo@pengaru.com \
/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.