From: Qu Wenruo <wqu@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: [PATCH 0/2] btrfs-progs: move block-group-tree out of experimental features
Date: Tue, 11 Apr 2023 10:31:04 +0800 [thread overview]
Message-ID: <cover.1681180159.git.wqu@suse.com> (raw)
People are complaining block-group-tree features are not accessible for
non-experimental builds.
So let's make it a stable feature.
Since we're here, it's also a good time to deprecate
-R|--runtime-features option.
Qu Wenruo (2):
btrfs-progs: mkfs: make -R|--runtime-features option deprecated
btrfs-progs: move block-group-tree out of experimental features
Documentation/btrfs-man5.rst | 6 ++++++
Documentation/btrfstune.rst | 4 ++--
Documentation/mkfs.btrfs.rst | 30 +++++++++---------------------
common/fsfeatures.c | 8 --------
mkfs/main.c | 3 ++-
tune/main.c | 18 ++++++++----------
6 files changed, 27 insertions(+), 42 deletions(-)
--
2.39.2
next reply other threads:[~2023-04-11 2:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 2:31 Qu Wenruo [this message]
2023-04-11 2:31 ` [PATCH 1/2] btrfs-progs: mkfs: make -R|--runtime-features option deprecated Qu Wenruo
2023-04-12 1:51 ` Neal Gompa
2023-04-12 2:15 ` Qu Wenruo
2023-04-13 12:04 ` Anand Jain
2023-04-13 16:32 ` David Sterba
2023-04-14 5:07 ` Anand Jain
2023-04-11 2:31 ` [PATCH 2/2] btrfs-progs: move block-group-tree out of experimental features Qu Wenruo
2023-04-12 1:49 ` Neal Gompa
2023-04-12 2:12 ` Qu Wenruo
2023-04-13 12:24 ` Anand Jain
2023-04-13 16:38 ` David Sterba
2023-04-13 22:53 ` Qu Wenruo
2023-04-14 5:10 ` Anand Jain
2023-04-13 16:20 ` [PATCH 0/2] " David Sterba
2023-04-13 22:55 ` Qu Wenruo
2023-04-13 23:25 ` 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=cover.1681180159.git.wqu@suse.com \
--to=wqu@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.