From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 5.2.1
Date: Fri, 26 Jul 2019 17:58:47 +0200 [thread overview]
Message-ID: <20190726155847.12970-1-dsterba@suse.com> (raw)
Hi,
btrfs-progs version 5.2.1 have been released. This is a bugfix release.
Changes:
* scrub status: fix ETA calculation after resume
* check: fix crash when using -Q
* restore: fix symlink owner restoration
* mkfs: fix regression with mixed block groups
* core: fix commit to process all delayed refs
* other:
* minor cleanups
* test updates
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:
Adam Borowski (1):
btrfs-progs: fix a printf format string fatal warning
David Sterba (7):
btrfs-progs: props: update descriptions
btrfs-progs: props: convert to C99 initializers
btrfs-progs: props: update help texts
btrfs-progs: tests: switch messages to _log
btrfs-progs: restore: fix chown of a symlink
btrfs-progs: update CHANGES for v5.2.1
Btrfs progs v5.2.1
Filipe Manana (1):
Btrfs-progs: mkfs, fix metadata corruption when using mixed mode
Grzegorz Kowal (2):
btrfs-progs: scrub: fix ETA calculation
btrfs-progs: scrub: fix status lines alignment
Josef Bacik (1):
btrfs-progs: deal with drop_progress properly in fsck
Naohiro Aota (1):
btrfs-progs: check: initialize qgroup_item_count in earlier stage
Omar Sandoval (1):
btrfs-progs: receive: get rid of unnecessary strdup()
Qu Wenruo (3):
btrfs-progs: Exhaust delayed refs and dirty block groups to prevent delayed refs lost
btrfs-progs: extent-tree: Unify the parameters of btrfs_inc_extent_ref()
btrfs-progs: tests: Avoid debug log populating stdout
next reply other threads:[~2019-07-26 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 15:58 David Sterba [this message]
2019-07-30 11:17 ` Btrfs progs release 5.2.1 Baruch Siach
2019-07-30 11:28 ` Holger Hoffstätte
2019-07-30 12:20 ` 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=20190726155847.12970-1-dsterba@suse.com \
--to=dsterba@suse.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).