Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Andrey Albershteyn <aalbersh@kernel.org>
To: linux-xfs@vger.kernel.org
Cc: Andrey Albershteyn <aalbersh@kernel.org>
Subject: [PATCH] xfsprogs: update release.sh with fixes from xfsdump
Date: Thu,  7 May 2026 17:06:00 +0200	[thread overview]
Message-ID: <20260507150602.1453418-1-aalbersh@kernel.org> (raw)

While updating release.sh in xfsdump repository (copy-pasting this
release.sh into xfsdump repo), I added a few minor fixes to the
release.sh. These are those fixes (basically diff -u without
s/xfsprogs/xfsdump).

Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>
---
 release.sh | 20 +++++++++-----------
 1 file changed, 9 insertions(+), 11 deletions(-)

diff --git a/release.sh b/release.sh
index 32084fb9fd90..c9b3c1b97fac 100755
--- a/release.sh
+++ b/release.sh
@@ -1,13 +1,6 @@
-#!/bin/sh
+#!/usr/bin/env bash
 #
 # Automate generation of a new release
-#
-# Need to first update these files:
-#
-# VERSION (with new version number)
-# docs/CHANGES (with changelog and version/date string)
-# configure.ac (with new version string)
-# debian/changelog (with new release entry, only for release version)
 
 set -e
 
@@ -50,8 +43,10 @@ prepare_mail() {
 	if [ -n "$LAST_HEAD" ]; then
 		if [ $branch == "master" ]; then
 			reason="$(git describe --abbrev=0 $branch) released"
+			for_next_update="\n\nThe for-next branch has also been updated to match the state of master."
 		else
 			reason="for-next updated to $(git log --oneline --format="%h" -1 $branch)"
+			for_next_update=""
 		fi;
 		cat << EOF > $mail_file
 To: linux-xfs@vger.kernel.org
@@ -67,9 +62,7 @@ The xfsprogs $branch branch in repository at:
 has just been updated.
 
 Patches often get missed, so if your outstanding patches are properly reviewed
-on the list and not included in this update, please let me know.
-
-The for-next branch has also been updated to match the state of master.
+on the list and not included in this update, please let me know.$(printf "%b" "$for_next_update")
 
 The new head of the $branch branch is commit:
 
@@ -199,3 +192,8 @@ if [ -n "$LAST_HEAD" ]; then
 	echo "Command to send ANNOUNCE email"
 	printf "\tneomutt -H $mail_file\n"
 fi
+if [ $KUP -ne 1 ]; then
+	echo "Don't forget to upload tarball:"
+	echo -e "\tkup put xfsprogs-${version}.tar.gz" \
+		"xfsprogs-${version}.tar.sign pub/linux/utils/fs/xfs/xfsprogs/"
+fi
-- 
2.51.2


             reply	other threads:[~2026-05-07 15:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 15:06 Andrey Albershteyn [this message]
2026-05-08  8:54 ` [PATCH] xfsprogs: update release.sh with fixes from xfsdump 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=20260507150602.1453418-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