From: Carlos Maiolino <cem@kernel.org>
To: "Holger Hoffstätte" <holger@applied-asynchrony.com>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [ANNOUNCE] xfsprogs-6.0.0 released
Date: Mon, 14 Nov 2022 17:35:06 +0100 [thread overview]
Message-ID: <20221114163506.vvebiubf5e5b5obx@andromeda> (raw)
In-Reply-To: <08c365c6-09f4-5af4-b242-7189d9f79921@applied-asynchrony.com>
On Mon, Nov 14, 2022 at 12:51:41PM +0100, Holger Hoffstätte wrote:
> On 2022-11-14 12:36, Carlos Maiolino wrote:
> > Hi folks,
> >
> > The xfsprogs repository at:
> >
> > git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
> >
> > has just been updated and tagged for a v6.0.0 release. The condensed changelog
> > since v6.0.0-rc0 is below.
> >
> > Tarballs are available at:
> >
> > https://www.kernel.org/pub/linux/utils/fs/xfs/xfsprogs/xfsprogs-6.0.0.tar.gz
> > https://www.kernel.org/pub/linux/utils/fs/xfs/xfsprogs/xfsprogs-6.0.0.tar.xz
> > https://www.kernel.org/pub/linux/utils/fs/xfs/xfsprogs/xfsprogs-6.0.0.tar.sign
> >
> > Patches often get missed, so please check if your outstanding
> > patches were in this update. If they have not been in this update,
> > please resubmit them to linux-xfs@vger.kernel.org so they can be
> > picked up in the next update.
>
> It looks like my compilation fix for clang-16 (and maybe gcc-13?) is missing:
>
> https://lore.kernel.org/linux-xfs/865733c7-8314-cd13-f363-5ba2c6842372@applied-asynchrony.com/
>
This should go into 6.1, I expect to push this and some more stuff into for-next
around this week, depending on how much time libxfs sync will consume.
> thanks
> Holger
--
Carlos Maiolino
next prev parent reply other threads:[~2022-11-14 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 11:36 [ANNOUNCE] xfsprogs-6.0.0 released Carlos Maiolino
2022-11-14 11:51 ` Holger Hoffstätte
2022-11-14 16:35 ` Carlos Maiolino [this message]
2022-11-14 19:16 ` Darrick J. Wong
2022-11-15 15:35 ` Carlos Maiolino
2022-11-15 23:18 ` 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=20221114163506.vvebiubf5e5b5obx@andromeda \
--to=cem@kernel.org \
--cc=holger@applied-asynchrony.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.