From: David Sterba <dsterba@suse.cz>
To: WorMzy Tykashi <wormzy.tykashi@gmail.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs-progs 3.19rc1 issues
Date: Wed, 4 Feb 2015 09:58:45 +0100 [thread overview]
Message-ID: <20150204085845.GE24227@suse.cz> (raw)
In-Reply-To: <CALOYprUOeeeeXTZwCjBDvC5rapM-Dk5xwQ26S9nVZWKaG2c1mA@mail.gmail.com>
On Tue, Feb 03, 2015 at 10:26:00PM +0000, WorMzy Tykashi wrote:
> I've been watching the 3.19.x branch with interest, and noticed that
> you've tagged rc1. Unfortunately, I think I've found a few problems
> with it. I will try to explain here:
Thanks for the early feedback, I did not manage to write the
announcement yesterday. The purpose of the release is to find the
problems that arise from the reworked build system. I'll look at the
issues.
prev parent reply other threads:[~2015-02-04 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-03 22:26 Btrfs-progs 3.19rc1 issues WorMzy Tykashi
2015-02-04 1:19 ` Qu Wenruo
2015-02-04 8:58 ` 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=20150204085845.GE24227@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).