public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [ANNOUNCE] xfsprogs-6.0.0 released
Date: Mon, 14 Nov 2022 11:16:26 -0800	[thread overview]
Message-ID: <Y3KUCsPH0rSv2Tzb@magnolia> (raw)
In-Reply-To: <20221114113639.mxgewf2zjgokr6cb@andromeda>

On Mon, Nov 14, 2022 at 12:36:39PM +0100, 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.

That means I should requeue this pile of bugfixes
https://lore.kernel.org/linux-xfs/166795950005.3761353.14062544433865007925.stgit@magnolia/T/#t

for 6.1, right?

--D

> The new head of the master branch is commit:
> 
> 3498b6802 xfsprogs: Release v6.0.0
> 
> New Commits:
> 
> Andrey Albershteyn (5):
>       [f103166a9] xfs_quota: separate quota info acquisition into get_dquot()
>       [2c1e7aefd] xfs_quota: separate get_dquot() and dump_file()
>       [79e651743] xfs_quota: separate get_dquot() and report_mount()
>       [6c007276a] xfs_quota: utilize XFS_GETNEXTQUOTA for ranged calls in report/dump
>       [f2fde322d] xfs_quota: apply -L/-U range limits in uid/gid/pid loops
> 
> Carlos Maiolino (1):
>       [3498b6802] xfsprogs: Release v6.0.0
> 
> Jakub Bogusz (1):
>       [f034a3215] Polish translation update for xfsprogs 5.19.0.
> 
> Xiaole He (1):
>       [d878935dd] xfs_db: use preferable macro to seek offset for local dir3 entry fields
> 
>  VERSION          |     2 +-
>  configure.ac     |     2 +-
>  db/dir2sf.c      |     6 +-
>  debian/changelog |     6 +
>  doc/CHANGES      |     5 +
>  po/pl.po         | 21351 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------------------------------------------------------------------------
>  quota/report.c   |   343 ++-
>  7 files changed, 11248 insertions(+), 10467 deletions(-)
> 
> 
> I needed to do a forced update to the tree, to fix a patch authoring mistake,
> since both push and forced push were done only a few minutes apart, I hope it
> didn't cause any trouble for anyone, otherwise, please accept my apologies.
> 
> -- 
> Carlos Maiolino

  parent reply	other threads:[~2022-11-14 19:16 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
2022-11-14 19:16 ` Darrick J. Wong [this message]
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=Y3KUCsPH0rSv2Tzb@magnolia \
    --to=djwong@kernel.org \
    --cc=cem@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