From: "Darrick J. Wong" <djwong@kernel.org>
To: Andrey Albershteyn <aalbersh@redhat.com>
Cc: linux-xfs@vger.kernel.org, Andrey Albershteyn <aalbersh@kernel.org>
Subject: Re: [PATCH 2/4] release.sh: add --kup to upload release tarball to kernel.org
Date: Thu, 16 Jan 2025 14:22:27 -0800 [thread overview]
Message-ID: <20250116222227.GD1611770@frogsfrogsfrogs> (raw)
In-Reply-To: <20250110-update-release-v1-2-61e40b8ffbac@kernel.org>
On Fri, Jan 10, 2025 at 12:05:07PM +0100, Andrey Albershteyn wrote:
> Signed-off-by: Andrey Albershteyn <aalbersh@kernel.org>
> ---
> release.sh | 31 +++++++++++++++++++++++++++++++
> 1 file changed, 31 insertions(+)
>
> diff --git a/release.sh b/release.sh
> index b15ed610082f34928827ab0547db944cf559cef4..a23adc47efa5163b4e0082050c266481e4051bfb 100755
> --- a/release.sh
> +++ b/release.sh
> @@ -16,6 +16,30 @@ set -e
> version=${PKG_MAJOR}.${PKG_MINOR}.${PKG_REVISION}
> date=`date +"%-d %B %Y"`
>
> +KUP=0
> +
> +help() {
> + echo "$(basename) - create xfsprogs release"
> + printf "\t[--kup|-k] upload final tarball with KUP\n"
> +}
> +
> +while [ $# -gt 0 ]; do
> + case "$1" in
> + --kup|-k)
> + KUP=1
> + ;;
> + --help|-h)
> + help
> + exit 0
> + ;;
> + *)
> + >&2 printf "Error: Invalid argument\n"
> + exit 1
> + ;;
> + esac
> + shift
> +done
> +
> echo "Cleaning up"
> make realclean
> rm -rf "xfsprogs-${version}.tar" \
> @@ -52,4 +76,11 @@ gpg \
>
> mv "xfsprogs-${version}.tar.asc" "xfsprogs-${version}.tar.sign"
>
> +if [ $KUP -eq 1 ]; then
> + kup put \
> + xfsprogs-${version}.tar.gz \
> + xfsprogs-${version}.tar.sign \
> + pub/linux/utils/fs/xfs/xfsprogs/xfsprogs-${version}.tar.gz
Shouldn't this last argument be "pub/linux/utils/fs/xfs/xfsprogs/" ?
also you might want to put a sentence in the commit log for why you
want this, e.g. "Add kup support so that the maintainer can push the
newly formed release taballs to kernel.org."
--D
> +fi;
> +
> echo "Done. Please remember to push out tags using \"git push origin v${version}\""
>
> --
> 2.47.0
>
>
next prev parent reply other threads:[~2025-01-16 22:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 11:05 [PATCH 0/4] Update release.sh Andrey Albershteyn
2025-01-10 11:05 ` [PATCH 1/4] release.sh: add signing and fix outdated commands Andrey Albershteyn
2025-01-16 21:43 ` Darrick J. Wong
2025-01-10 11:05 ` [PATCH 2/4] release.sh: add --kup to upload release tarball to kernel.org Andrey Albershteyn
2025-01-16 22:22 ` Darrick J. Wong [this message]
2025-01-20 10:59 ` Andrey Albershteyn
2025-01-10 11:05 ` [PATCH 3/4] release.sh: update version files make commit optional Andrey Albershteyn
2025-01-16 22:33 ` Darrick J. Wong
2025-01-20 11:53 ` Andrey Albershteyn
2025-01-22 1:45 ` Darrick J. Wong
2025-01-10 11:05 ` [PATCH 4/4] release.sh: generate ANNOUNCE email Andrey Albershteyn
2025-01-16 22:41 ` Darrick J. Wong
2025-01-20 12:14 ` Andrey Albershteyn
2025-01-22 2:02 ` Darrick J. Wong
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=20250116222227.GD1611770@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=aalbersh@kernel.org \
--cc=aalbersh@redhat.com \
--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