All of lore.kernel.org
 help / color / mirror / Atom feed
From: Piergiorgio Sartor <piergiorgio.sartor-i47jiTeKxPI@public.gmane.org>
To: Maurits van de Lande <maurits-16bHRcU+HuelQ9BUahrlcQ@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: current status of bcache
Date: Tue, 1 May 2012 15:28:56 +0200	[thread overview]
Message-ID: <20120501132856.GA10648@lazy.lzy> (raw)
In-Reply-To: <001601cd279c$b4a66e80$1df34b80$@com>

BTW,

as far as I know bcache is in "staging", is it?

Is there any schedule or plan on how it will be
taken out of staging to "stable"?

The reason is that some Linux distributions seem
to refrain to enable drivers in staging, so it
would be nice to have an idea if it is worth to
recompile the kernel or wait.

Thanks,

bye,

pg

On Tue, May 01, 2012 at 03:17:06PM +0200, Maurits van de Lande wrote:
> Hello,
> 
> The website bcache.evilpiepirate.org is a bit stale. What is the current
> status of bcache and where can I download the latest (stable) source code?
> Can it be compiled on Centos 6? Is it production ready?
> 
> Thanks!
> 
> Best regards,
> 
> Maurits van de Lande
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bcache" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 

piergiorgio

      reply	other threads:[~2012-05-01 13:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E05DC6BC8CD98846BCBC2D7FEE836A383459C324@E2k10-MBS1.VDL-Fittings.local>
     [not found] ` <E05DC6BC8CD98846BCBC2D7FEE836A383459C324-1/w6Wl7DZ0EnXB/+/wfNbLrATFufUpkqjY/Qatn5Fs8@public.gmane.org>
2012-05-01 13:17   ` current status of bcache Maurits van de Lande
2012-05-01 13:28     ` Piergiorgio Sartor [this message]

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=20120501132856.GA10648@lazy.lzy \
    --to=piergiorgio.sartor-i47jitekxpi@public.gmane.org \
    --cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=maurits-16bHRcU+HuelQ9BUahrlcQ@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.