From: David Sterba <dsterba@suse.cz>
To: WorMzy Tykashi <wormzy.tykashi@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs-progs releases
Date: Mon, 29 Sep 2014 16:25:32 +0200 [thread overview]
Message-ID: <20140929142532.GA11436@suse.cz> (raw)
In-Reply-To: <CALOYprVLH2e4Ujp-iN6CTFzTVi1x4VwayRgpvQEkmwNBbNXEWQ@mail.gmail.com>
On Thu, Sep 18, 2014 at 10:38:03PM +0100, WorMzy Tykashi wrote:
> 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?
The patch flow should stay as is for now, ie. integration branches at
the current repos. The kernel.org repo will serve as release repository
only.
prev parent reply other threads:[~2014-09-29 14:25 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
2014-09-29 14:25 ` David Sterba [this message]
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=20140929142532.GA11436@suse.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wormzy.tykashi@gmail.com \
/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).