From: Eric Sandeen <sandeen@redhat.com>
To: Chris Mason <chris.mason@fusionio.com>, linux-btrfs@vger.kernel.org
Subject: Re: btrfs-progs tagged as v3.12
Date: Tue, 26 Nov 2013 09:05:24 -0600 [thread overview]
Message-ID: <5294B8B4.5030407@redhat.com> (raw)
In-Reply-To: <20131125214534.8160.40797@ret.masoncoding.com>
On 11/25/13, 3:45 PM, Chris Mason wrote:
> Hi everyone,
>
> I've tagged the current btrfs-progs repo as v3.12. The new idea is that
> instead of making the poor distros pull from git, I'll be creating
> tagged releases at roughly the same pace as Linus cuts kernels.
>
> Given the volume of btrfs-progs patches, we should have enough new code
> and fixes to justify releases at least as often as the kernel. Of
> course, if there are issues that need immediate attention, I'll tag a .y
> release (v3.12.1 for example).
>
> If the progs changes slow down, we might skip a version. But tracking
> kernel version numbers makes it easier for me to line up bug reports,
> mostly because I already devote a fair number of brain cells to
> remembering how old each kernel is.
>
> Just let me know if there are any questions.
Cool! I've built it for Fedora 19, 20, and rawhide, updates should
trickle out soon.
-Eric
next prev parent reply other threads:[~2013-11-26 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 21:45 btrfs-progs tagged as v3.12 Chris Mason
2013-11-25 22:46 ` Martin
2013-11-26 15:05 ` Eric Sandeen [this message]
2013-11-27 11:28 ` Tom Gundersen
2014-03-20 23:36 ` WorMzy Tykashi
2014-03-20 23:55 ` Chris Mason
2014-03-21 0:00 ` WorMzy Tykashi
2014-04-06 20:14 ` Sébastien Luttringer
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=5294B8B4.5030407@redhat.com \
--to=sandeen@redhat.com \
--cc=chris.mason@fusionio.com \
--cc=linux-btrfs@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.