public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 6.7.1
Date: Wed, 14 Feb 2024 07:56:29 +0100	[thread overview]
Message-ID: <20240214065632.26487-1-dsterba@suse.com> (raw)

Hi,

btrfs-progs version 6.7.1 have been released. This is a bugfix release.

You may note a change on the RTD site that some links got fixed and no longer
point to a document that is included to multiple sources. Eg. the link to
'Typical use cases' on page btrfs-device.html stays there, previously it ended
up in ch-volume-management-intro.html (the same section is also on the Volume
management page). If you find other broken links or formatting bugs, please
report them.

Changelog:
   * convert: raid-stripe-tree can be now enabled for the target filesystem
   * mkfs:
      * handle lifetime of open file descriptors so it does not trigger udev
        that could miss to create the UUID symlinks in /dev
      * update warning when CPU page size does not match sector size
      * merge features in summary, no more distinction of incompat and runtime
        to match the semantics of option -O
   * fi show: fix recognizing raw device mapper paths
   * other:
      * CI updates, build images updates
      * minor cleanups
      * minor sync with kernel
      * documentation updates, fix links to labels in included directories

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
Release: https://github.com/kdave/btrfs-progs/releases/tag/v6.7.1

                 reply	other threads:[~2024-02-14  6:57 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=20240214065632.26487-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