From: Kent Overstreet <kmo@daterainc.com>
To: "Paul B. Henson" <henson@acm.org>
Cc: linux-bcache@vger.kernel.org
Subject: Re: stable bcache-tools?
Date: Sat, 23 Nov 2013 17:05:37 -0800 [thread overview]
Message-ID: <20131124010537.GF20624@moria.home.lan> (raw)
In-Reply-To: <002001cee7f2$0868a260$1939e720$@acm.org>
On Fri, Nov 22, 2013 at 06:16:23PM -0800, Paul B. Henson wrote:
> Is there going to be a release cut of bcache-tools at some point so
> distributions could have a stable version to package? Is the current git
> head pretty much considered production ready and bug free?
The current git head should be completely fine for production usage -
there's not really anything complicated enough (save the udev stuff,
maybe) to merit tagging a specific version as stable. I suppose
distributions could use some kind of hint that useful changes have gone
in and they should package a new version - anything in particular you
want there?
next prev parent reply other threads:[~2013-11-24 1:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-23 2:16 stable bcache-tools? Paul B. Henson
2013-11-24 1:05 ` Kent Overstreet [this message]
2013-11-24 20:46 ` Paul B. Henson
2013-11-25 0:55 ` Kent Overstreet
2013-11-26 2:10 ` Paul B. Henson
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=20131124010537.GF20624@moria.home.lan \
--to=kmo@daterainc.com \
--cc=henson@acm.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox