From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 5.18.1
Date: Mon, 6 Jun 2022 19:20:16 +0200 [thread overview]
Message-ID: <20220606172016.320-1-dsterba@suse.com> (raw)
Hi,
btrfs-progs version 5.18.1 have been released. This is a bugfix release.
Changelog:
* fixes:
* convert: fix self reference of toplevel directory
* build: make kernel lib headers compatible with C++
* zoned mode: verify minimum zone size 4MiB
* libbtrfs: cleanups, merge headers and remove declarations of unexported
symbols
* other: documentation 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:
David Sterba (15):
btrfs-progs: docs: add link to released tarballs
btrfs-progs: kernel-lib: make headers C++ compatible
btrfs-progs: docs: reformat btrfs-property manual page
btrfs-progs: convert: fix self-reference of directory
btrfs-progs: docs: update Gloassary
btrfs-progs: libbtrfs: add clean targets
btrfs-progs: libbtrfs: use own copy of ctree.h, extent_io.h, send.h and extent-cache.h
btrfs-progs: libbtrfs: drop ifdef BTRFS_FLAT_INCLUDES where not necessary
btrfs-progs: libbtrfs: remove declarations without exports in send-utils
btrfs-progs: libbtrfs: remove declarations without exports in extent_io.h
btrfs-progs: libbtrfs: remove declarations without exports in extent-cache.h
btrfs-progs: libbtrfs: move extent_io.h to ctree.h
btrfs-progs: libbtrfs: move extent-cache.h to ctree.h
btrfs-progs: update CHANGES for 5.18.1
Btrfs progs v5.18.1
Johannes Thumshirn (1):
btrfs-progs: zoned: add upper and lower zone size boundaries
frukto (2):
btrfs-progs: docs: fix typo in mkfs.btrfs
btrfs-progs: docs: make description of list output more clear
reply other threads:[~2022-06-06 17:24 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=20220606172016.320-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