From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 5.10.1
Date: Fri, 5 Feb 2021 12:25:06 +0100 [thread overview]
Message-ID: <20210205112506.4274-1-dsterba@suse.com> (raw)
Hi,
btrfs-progs version 5.10.1 have been released.
The static build got broken due to libmount added in 5.10, this works now. The
minimum libmount version is 2.24 that is not available on some LTS distros like
CentOS 7. The plan is to bring the support back, reimplementing some libmount
functionality and dropping the dependency again.
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 (6):
btrfs-progs: build: fix linking with static libmount
btrfs-progs: tests: add support to test the .static binaries
btrfs-progs: docs: clarify scrub requiring mounted filesystem
btrfs-progs: INSTALL: update build dependencies
btrfs-progs: update CHANGES for 5.10.1
Btrfs progs v5.10.1
next reply other threads:[~2021-02-05 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 11:25 David Sterba [this message]
2021-02-16 11:00 ` Btrfs progs release 5.10.1 Filipe Manana
2021-02-19 19:38 ` 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=20210205112506.4274-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).