From: Andrey Albershteyn <aalbersh@kernel.org>
To: linux-xfs@vger.kernel.org
Cc: Andrey Albershteyn <aalbersh@kernel.org>
Subject: [PATCH 0/2] xfsdump: improve tooling
Date: Wed, 6 May 2026 18:37:42 +0200 [thread overview]
Message-ID: <20260506163746.1083845-1-aalbersh@kernel.org> (raw)
Hi all,
First patch fixes Makefile for systems with read-only system packages.
The second patch copy-pastes release.sh from xfsprogs-dev repository
with a few minor improvements (I will send these for xfsprogs too).
xfsdump git tree:
https://git.kernel.org/pub/scm/linux/kernel/git/aalbersh/xfsdump-dev.git/log/?h=better-release
Andrey
Andrey Albershteyn (2):
xfsdump: fix permissions on files installed by libtoolize
xfsdump: update release.sh
Makefile | 3 +
release.sh | 197 +++++++++++++++++++++++++++++++++++---
tools/git-contributors.py | 168 ++++++++++++++++++++++++++++++++
3 files changed, 354 insertions(+), 14 deletions(-)
create mode 100755 tools/git-contributors.py
--
2.51.2
next reply other threads:[~2026-05-06 16:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 16:37 Andrey Albershteyn [this message]
2026-05-06 16:37 ` [PATCH 1/2] xfsdump: fix permissions on files installed by libtoolize Andrey Albershteyn
2026-05-07 5:34 ` Christoph Hellwig
2026-05-06 16:37 ` [PATCH 2/2] xfsdump: update release.sh Andrey Albershteyn
2026-05-07 5:34 ` Christoph Hellwig
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=20260506163746.1083845-1-aalbersh@kernel.org \
--to=aalbersh@kernel.org \
--cc=linux-xfs@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