Linux XFS filesystem development
 help / color / mirror / Atom feed
From: Carlos Maiolino <cem@kernel.org>
To: linux-xfs@vger.kernel.org
Subject: [ANNOUNCE] xfsprogs: for-next updated to b894e1b9a
Date: Mon, 26 Jun 2023 14:07:36 +0200	[thread overview]
Message-ID: <20230626120736.4bccaypfhqbgsoqc@andromeda> (raw)

Hello.

The xfsprogs for-next branch, located at:

https://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git/refs/?h=for-next

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 new head of the for-next branch is commit:

b894e1b9a567338f62eefb6d6ea0290d0b37060d

4 new commits:

David Seifert (1):
      [987373623] po: Fix invalid .de translation format string

Donald Douwsma (1):
      [248754271] xfstests: add test for xfs_repair progress reporting

Pavel Reichl (1):
      [b894e1b9a] mkfs: fix man's default value for sparse option

Weifeng Su (1):
      [8813e12cc] libxcmd: add return value check for dynamic memory function

Code Diffstat:

 libxcmd/command.c      |  4 +++
 man/man8/mkfs.xfs.8.in |  2 +-
 po/de.po               |  2 +-
 tests/xfs/999          | 66 ++++++++++++++++++++++++++++++++++++++++++++++++++
 tests/xfs/999.out      | 15 ++++++++++++
 5 files changed, 87 insertions(+), 2 deletions(-)
 create mode 100755 tests/xfs/999
 create mode 100644 tests/xfs/999.out

-- 
Carlos

             reply	other threads:[~2023-06-26 12:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-26 12:07 Carlos Maiolino [this message]
2023-06-28  3:23 ` [ANNOUNCE] xfsprogs: for-next updated to b894e1b9a 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=20230626120736.4bccaypfhqbgsoqc@andromeda \
    --to=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