Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 23 Oct 2018 05:14:18 +0100
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.
Message-ID: <20181023041418.GU32577@ZenIV.linux.org.uk>
References: <20181022101912.3CE2E292B005@huitzilopochtli.metztli-it.com>
 <20181023033852.GR32577@ZenIV.linux.org.uk>
 <20181023034719.tqkvdj2eakh2uh2q@shells.gnugeneration.com>
 <20181023035425.GS32577@ZenIV.linux.org.uk>
 <20181023040418.iz7gcph3qha4bkab@shells.gnugeneration.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20181023040418.iz7gcph3qha4bkab@shells.gnugeneration.com>
User-Agent: Mutt/1.9.1 (2017-09-22)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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.