From: Andrew Price <anprice@redhat.com>
To: gfs2@lists.linux.dev, users@clusterlabs.org, developers@clusterlabs.org
Subject: Re: gfs2-utils 3.6.0 released
Date: Thu, 27 Feb 2025 11:26:46 +0000 [thread overview]
Message-ID: <797dc02a-3b93-4b5c-9ba6-b7514fa9cfb4@redhat.com> (raw)
In-Reply-To: <8f91c89d-609c-4398-b03d-49d3ff975f73@redhat.com>
It turns out that the .bz2 and .xz tarballs for gfs2-utils 3.6.0 were
not compressed due to missing 'git archive' config options for those
schemes. I've updated the release steps to prevent that from happening
in future. As Pagure doesn't allow re-uploading release tarballs I'll do
a follow-up 3.6.1 release today.
Andy
prev parent reply other threads:[~2025-02-27 11:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-26 17:27 gfs2-utils 3.6.0 released Andrew Price
2025-02-27 11:26 ` Andrew Price [this message]
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=797dc02a-3b93-4b5c-9ba6-b7514fa9cfb4@redhat.com \
--to=anprice@redhat.com \
--cc=developers@clusterlabs.org \
--cc=gfs2@lists.linux.dev \
--cc=users@clusterlabs.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