From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Cc: clm@fb.com
Subject: Btrfs progs pre-release 3.18-rc2
Date: Fri, 19 Dec 2014 19:21:30 +0100 [thread overview]
Message-ID: <20141219182130.GL27601@twin.jikos.cz> (raw)
Hi
another step towards 3.18, the changes are limited in scope and mostly
cleanups or docs. I'd like to see more test images for new fsck code,
there are 2 new that I missed earlier, so they don't count.
The timing with end of the year is not good so if I'm not confident
that the release is in a good shape I'm rather going to postpone it.
Alternatively, I can do a release on Monday and then use the following
weeks to prepare a .1 bugfix release.
Known problems: the image 013 fails
next reply other threads:[~2014-12-19 18:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-19 18:21 David Sterba [this message]
2014-12-22 8:17 ` Btrfs progs pre-release 3.18-rc2 Qu Wenruo
2014-12-22 11:37 ` David Sterba
2014-12-23 0:33 ` Qu Wenruo
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=20141219182130.GL27601@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=clm@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox