All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Stephen R. van den Berg" <srb@cuci.nl>
To: Kent Overstreet <kmo@daterainc.com>
Cc: linux-bcache@vger.kernel.org
Subject: Re: 3.18.1 + latest bcache-dev
Date: Tue, 6 Jan 2015 10:16:25 +0100	[thread overview]
Message-ID: <20150106091625.GA8154@cuci.nl> (raw)
In-Reply-To: <20150105110602.GA31622@kmo-pixel>

Kent Overstreet wrote:
>On Mon, Jan 05, 2015 at 09:49:19AM +0100, Stephen R. van den Berg wrote:
>> Kent Overstreet wrote:
>> >Yes, correct. The on disk format changes in bcache-dev are just too deep to
>> >feasibly write backwards compat code, unfortunately.

>> >And the on disk format is still in flux - for just a bit longer hopefully
>> >though, right now I'm working on a pretty major revamp that's getting close to

>> Any chance we could get a git url of the bcache-tools-in-flux as well?

>Yeah, I just pushed the current (very much WIP) stuff to the bcache-dev branch
>under the main bcache-tools repo

Maybe I'm not looking in the right spot, but I do not see that branch.
What is the main bcache-tools repo?
-- 
Stephen.

  reply	other threads:[~2015-01-06  9:16 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
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 [this message]
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=20150106091625.GA8154@cuci.nl \
    --to=srb@cuci.nl \
    --cc=kmo@daterainc.com \
    --cc=linux-bcache@vger.kernel.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.