From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Cc: clm@fb.com
Subject: Btrfs progs release 4.10.2
Date: Fri, 31 Mar 2017 17:34:15 +0200 [thread overview]
Message-ID: <20170331153415.2287-1-dsterba@suse.com> (raw)
Hi,
btrfs-progs version 4.10.2 have been released. More build breakages fixed and
some minor updates.
Changes:
* check: lowmem mode fix for false alert about lost backrefs
* convert: minor bugfix
* library: fix build, misisng symbols, added tests
Tarballs: https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/
Git: git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git
Shortlog:
David Sterba (4):
btrfs-progs: library-test: add all exported headers
btrfs-progs: add prefix to message helpers
btrfs-progs: update CHANGES for v4.10.2
Btrfs progs v4.10.2
Qu Wenruo (4):
btrfs-progs: Cleanup kernel-shared dir when execute make clean
btrfs-progs: convert: Add missing return for HOLE mode when checking convert image
btrfs-progs: check: lowmem, fix false alert about backref lost for SHARED_DATA_REF
btrfs-progs: tests: Add SHARED_DATA_REF test image for check lowmem mode
Sergei Trofimovich (1):
btrfs-progs: fix missing __error symbol in libbtrfs.so.0
reply other threads:[~2017-03-31 15:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20170331153415.2287-1-dsterba@suse.com \
--to=dsterba@suse.com \
--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;
as well as URLs for NNTP newsgroup(s).