linux-bcache.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rolf Fokkens <rolf@rolffokkens.nl>
To: Kent Overstreet <kmo@daterainc.com>,
	Eric Wheeler <bcache@lists.ewheeler.net>
Cc: Slava Pestov <sp@datera.io>,
	"Stephen R. van den Berg" <srb@cuci.nl>,
	linux-bcache@vger.kernel.org
Subject: Re: 3.18.1 + latest bcache-dev
Date: Thu, 08 Jan 2015 20:47:44 +0100	[thread overview]
Message-ID: <54AEDEE0.9090601@rolffokkens.nl> (raw)
In-Reply-To: <20150108023054.GB1263@kmo-pixel>

On 01/08/2015 03:30 AM, Kent Overstreet wrote:
> On Wed, Jan 07, 2015 at 12:17:19PM -0800, Eric Wheeler wrote:
>> Would it make sense to call this bcache2 and merge both into the 
>> linux tree once bcache2 is stable enough for broader testing? 
> Yeah that might be what happens.
I would be very much in favour if this approach. The (temporary) 
availability of both bcache and bcache2 gives users not only time to 
test it, but to migrate as well.

  reply	other threads:[~2015-01-08 19:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-28  2:35 3.18.1 + latest bcache-dev Stephen R. van den Berg
2014-12-29  4:05 ` Slava Pestov
2015-01-03 16:40   ` Rolf Fokkens
2015-01-04  0:46     ` Kent Overstreet
2015-01-04 14:11       ` Rolf Fokkens
2015-01-05  7:47         ` Slava Pestov
2015-01-06 22:18           ` Rolf Fokkens
2015-01-06 22:47             ` Slava Pestov
2015-01-07  1:48             ` Kent Overstreet
2015-01-07 17:41               ` Jianjian Huo
2015-01-08  2:29                 ` Kent Overstreet
2015-01-07 20:17             ` Eric Wheeler
2015-01-08  2:30               ` Kent Overstreet
2015-01-08 19:47                 ` Rolf Fokkens [this message]
2015-01-05  8:49       ` Stephen R. van den Berg
2015-01-05 11:06         ` Kent Overstreet
2015-01-06  9:16           ` Stephen R. van den Berg
2015-01-06 11:10             ` 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=54AEDEE0.9090601@rolffokkens.nl \
    --to=rolf@rolffokkens.nl \
    --cc=bcache@lists.ewheeler.net \
    --cc=kmo@daterainc.com \
    --cc=linux-bcache@vger.kernel.org \
    --cc=sp@datera.io \
    --cc=srb@cuci.nl \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).