From: WorMzy Tykashi <wormzy.tykashi@gmail.com>
To: David Sterba <dsterba@suse.cz>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs-progs releases
Date: Thu, 18 Sep 2014 22:38:03 +0100 [thread overview]
Message-ID: <CALOYprVLH2e4Ujp-iN6CTFzTVi1x4VwayRgpvQEkmwNBbNXEWQ@mail.gmail.com> (raw)
In-Reply-To: <53FC982B.9090608@fb.com>
On 26 August 2014 15:22, Chris Mason <clm@fb.com> wrote:
> Hi everyone,
>
> I've just tagged btrfs-progs v3.16. Like the last few releases, this
> one was prepared by Dave Sterba, who has been wrangling btrfs-progs
> patches for some time now.
>
> Dave has asked to officially take over the btrfs-progs maintenance, and
> I said yes before he could change his mind. Everyone here is doing a
> fantastic job improving btrfs-progs quality and usability, and making
> Dave the btrfs progs maintainer will make sure these changes get
> out on a regular basis.
>
> Aside from more regular releases, very little will change. I'm still
> running the kernel releases, and I'm setting up more frequent pushes to
> the kernel integration branch so we can more effectively manage our
> patches for the next merge window.
>
> While Dave is getting his kernel.org accounts setup, I'll keep pushing
> his changes to my btrfs-progs git tree, and create tar balls in the
> usual places.
>
> Once his kernel.org trees are setup, we'll find a way to mirror his
> master copy into my directories.
>
> Thanks for your contributions everyone, please let us know if you have
> any questions.
>
> -chris
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi David,
Congrats (?) on taking over the btrfs-progs releases!
I was wondering if you could shed some light on the status of the
integration branches. Are these going to be discontinued now that you
are maintaining and tagging the official btrfs-progs releases, or will
they stick around, serving a similar purpose as before?
Cheers,
WorMzy Tykashi
next prev parent reply other threads:[~2014-09-18 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 14:22 Btrfs-progs releases Chris Mason
2014-09-18 21:38 ` WorMzy Tykashi [this message]
2014-09-29 14:25 ` David Sterba
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=CALOYprVLH2e4Ujp-iN6CTFzTVi1x4VwayRgpvQEkmwNBbNXEWQ@mail.gmail.com \
--to=wormzy.tykashi@gmail.com \
--cc=dsterba@suse.cz \
--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 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).