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.2.2
Date: Sat, 25 Mar 2023 20:12:16 +0100	[thread overview]
Message-ID: <20230325191216.23500-1-dsterba@suse.com> (raw)

Hi,

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

Changelog:
   * fix build on old x86 architectures with builtin crypto
   * device stats: fix printing wrong values in tabular output
   * qgroup show: fix qgroup id formatting in json output
   * restore: fix restoring xattrs on directories
   * restore: don't modify metadata in dry-run mode
   * balance: fix some cases wrongly parsed as old syntax
   * balance: warn when deprecated syntax is used
   * seeding: fall back to old way if sysfs device fsid is not available
   * convert: handle orphan file ext4 feature
   * other:
      * sync ioctl definitions
      * enable github CI
      * update documentation

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

                 reply	other threads:[~2023-03-25 19:18 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=20230325191216.23500-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).