From: wangmy@fujitsu.com
To: openembedded-core@lists.openembedded.org
Cc: Wang Mingyu <wangmy@cn.fujitsu.com>
Subject: [OE-core] [PATCH 03/20] btrfs-tools: upgrade 6.11 -> 6.12
Date: Tue, 10 Dec 2024 07:56:35 +0800 [thread overview]
Message-ID: <1733788612-20933-3-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1733788612-20933-1-git-send-email-wangmy@fujitsu.com>
From: Wang Mingyu <wangmy@cn.fujitsu.com>
Changelog:
============
* subvolume delete: add new option to do recursive subvolume deletion (for
regular user delete only accessible subvolumes)
* mkfs:
* new option --subvol to create subvolumes in given paths, read-write,
read-only and default
* add hard link detection support for --rootdir option
* fixes:
* receive: message verbosity fixes
* check: fix false positive report of missing checksum for extent holes
* check: handle compressed extents when checking tree log
* when asking Y/N user questions, flush the terminal so the question is
displayed (e.g. btrfstune -S)
* other
* code refactoring, error handling
* python packaging fixes
* documentation updates
* new tests
Signed-off-by: Wang Mingyu <wangmy@cn.fujitsu.com>
---
.../btrfs-tools/{btrfs-tools_6.11.bb => btrfs-tools_6.12.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/btrfs-tools/{btrfs-tools_6.11.bb => btrfs-tools_6.12.bb} (98%)
diff --git a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.11.bb b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.12.bb
similarity index 98%
rename from meta/recipes-devtools/btrfs-tools/btrfs-tools_6.11.bb
rename to meta/recipes-devtools/btrfs-tools/btrfs-tools_6.12.bb
index fa0599d28d..3c0bb81f75 100644
--- a/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.11.bb
+++ b/meta/recipes-devtools/btrfs-tools/btrfs-tools_6.12.bb
@@ -18,7 +18,7 @@ DEPENDS = "util-linux zlib"
SRC_URI = "git://github.com/kdave/btrfs-progs.git;branch=master;protocol=https \
file://0001-Add-a-possibility-to-specify-where-python-modules-ar.patch \
"
-SRCREV = "8859114eaee39c117ff95f5b60b4e81fc22f96e7"
+SRCREV = "85ca0a6d60c14eefda509970a26616ff16115612"
S = "${WORKDIR}/git"
PACKAGECONFIG ??= " \
--
2.34.1
next prev parent reply other threads:[~2024-12-09 23:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 23:56 [OE-core] [PATCH 01/20] barebox-tools: upgrade 2024.10.0 -> 2024.12.0 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 02/20] bash-completion: upgrade 2.14.0 -> 2.15.0 wangmy
2024-12-09 23:56 ` wangmy [this message]
2024-12-09 23:56 ` [OE-core] [PATCH 04/20] ell: upgrade 0.70 -> 0.71 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 05/20] git: upgrade 2.47.0 -> 2.47.1 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 06/20] gnupg: upgrade 2.5.1 -> 2.5.2 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 07/20] gstreamer1.0: upgrade 1.24.9 -> 1.24.10 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 08/20] hwdata: upgrade 0.389 -> 0.390 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 09/20] kexec-tools: upgrade 2.0.29 -> 2.0.30 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 10/20] libdrm: upgrade 2.4.123 -> 2.4.124 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 11/20] libsdl2: upgrade 2.30.9 -> 2.30.10 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 12/20] llvm: upgrade 19.1.4 -> 19.1.5 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 13/20] pixman: upgrade 0.44.0 -> 0.44.2 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 14/20] re2c: upgrade 4.0 -> 4.0.1 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 15/20] sqlite3: upgrade 3.47.0 -> 3.47.2 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 16/20] stress-ng: upgrade 0.18.06 -> 0.18.07 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 17/20] sudo: upgrade 1.9.16p1 -> 1.9.16p2 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 18/20] systemd-boot: upgrade 256.8 -> 256.9 wangmy
2024-12-10 11:03 ` Alexander Kanavin
2024-12-09 23:56 ` [OE-core] [PATCH 19/20] ttyrun: upgrade 2.35.0 -> 2.36.0 wangmy
2024-12-09 23:56 ` [OE-core] [PATCH 20/20] vte: upgrade 0.78.1 -> 0.78.2 wangmy
2024-12-10 12:54 ` [OE-core] [PATCH 01/20] barebox-tools: upgrade 2024.10.0 -> 2024.12.0 Mathieu Dubois-Briand
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=1733788612-20933-3-git-send-email-wangmy@fujitsu.com \
--to=wangmy@fujitsu.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=wangmy@cn.fujitsu.com \
/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