From: Christoph Hellwig <hch@lst.de>
To: joern@logfs.org, prasadjoshi.linux@gmail.com
Cc: logfs@logfs.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: state of logfs?
Date: Tue, 5 Apr 2016 14:54:48 +0200 [thread overview]
Message-ID: <20160405125448.GA3092@lst.de> (raw)
Logfs was introduced to the kernel in 2009, and hasn't seen any non-drive
by changes since 2012, while having lots of unsolved issues all over.
Is there any good reason to keep it in the tree?
reply other threads:[~2016-04-05 12:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20160405125448.GA3092@lst.de \
--to=hch@lst.de \
--cc=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logfs@logfs.org \
--cc=prasadjoshi.linux@gmail.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.