All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 24 Nov 2013 16:55:59 -0800	[thread overview]
Message-ID: <20131125005559.GC9244@kmo-pixel> (raw)
In-Reply-To: <20131124204637.GJ5195@bender.unx.csupomona.edu>

On Sun, Nov 24, 2013 at 12:46:37PM -0800, Paul B. Henson wrote:
> On Sat, Nov 23, 2013 at 05:05:37PM -0800, Kent Overstreet wrote:
> 
> > 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?
> 
> No, it's just that my distribution, Gentoo, only has the option of a
> stale snapshot from months ago or a live build that just pulls git head.
> In general, I just like stable software to have tagged releases, so
> distributions can ship the same stuff. The maintainer of mcelog, for
> example, doesn't tag releases, and expects distributions to just grab
> whatever's there the day they package, so there's really no continuity
> between distributions as far as what you end up with. There doesn't even
> need to be a tarball packaged or anything, just a simple tag in git
> identifying a "release" so distributions can package it.

Heh, I see. Ok, I'll tag a release :p

(there really should be some standardized announce mechanism/channel
from packages -> distros. hrm).

  reply	other threads:[~2013-11-25  0:55 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
2013-11-24 20:46   ` Paul B. Henson
2013-11-25  0:55     ` Kent Overstreet [this message]
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=20131125005559.GC9244@kmo-pixel \
    --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 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.