linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 6.5.2
Date: Tue,  3 Oct 2023 19:51:10 +0200	[thread overview]
Message-ID: <20231003175112.9571-1-dsterba@suse.com> (raw)

Hi,

btrfs-progs version 6.5.2 have been released. This is a sync release for
upcoming kernel features for 6.7, no important fixes are present and update is
not required.

Changelog:

* new feature support:
  * raid-stripe-tree, new tree to track extent mapping for raid profiles,
    allows raid1*, raid0 and raid10 on zoned devices (kernel 6.7)
  * simple quotas, simplified accounting that does not track exclusive and
    shared extents (kernel 6.7)
  * mkfs with duplicate UUID on a single device, temp-fsid (kernel 6.7)
* metadata_uuid: enhanced capabilities to repair partially updated fsid on
  multiple devices
* other:
   * updated tests and CI
   * sync sources with kernel

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.5.2

                 reply	other threads:[~2023-10-03 17: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=20231003175112.9571-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).