From: "Aaron W. Hsu" <arcfide-5nC73gNclPNzbRFIqnYvSA@public.gmane.org>
To: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Project Status
Date: Sun, 16 Dec 2012 16:00:13 -0500 [thread overview]
Message-ID: <kalcpa$v3p$1@ger.gmane.org> (raw)
In-Reply-To: 50CE31A3.1040706@networklabs.co.nz
Andrew Thrift wrote:
> I have noticed a slowdown in GIT commits, no updates to the bcache
> website since July and no mailing list activity since mid November.
>
> Is this project being actively developed ?
>
> A while back, there were talks of bcache becoming part of the mainline
> Kernel. Is this still happening ?
I would also like to bump this. I have wanted to play with and incorporate
bcache into my installations for a while, but things seemed to be in a
constant state of flux, and I was hoping that bcache would end up in the
mainline Linux kernel by now, but I haven't found any word as to what is
happening on that front.
I would love to know what the state of things is. It's hard for me to know
what kernels bcache can be used for, how to use it, and the status of
integration into the mainline kernel.
--
Aaron W. Hsu | arcfide-5nC73gNclPNzbRFIqnYvSA@public.gmane.org | http://www.sacrideo.us
Programming is just another word for the lost art of thinking.
next prev parent reply other threads:[~2012-12-16 21:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-16 20:40 Project Status Andrew Thrift
2012-12-16 21:00 ` Aaron W. Hsu [this message]
2012-12-18 19:05 ` Kent Overstreet
2012-12-19 20:43 ` Aaron W. Hsu
-- strict thread matches above, loose matches on Subject: below --
2025-09-13 5:07 Project status Carlos Rodriguez-Fernandez
2025-09-25 16:08 ` Chris Li
2025-09-25 16:37 ` Carlos Rodriguez-Fernandez
2011-05-18 1:53 Bostjan Skufca
[not found] ` <BANLkTi=jN+LbygKQfUeneytfKXa_LovEqw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-05-20 1:11 ` Kent Overstreet
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='kalcpa$v3p$1@ger.gmane.org' \
--to=arcfide-5nc73gnclpnzbrfiqnyvsa@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.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.