From: Eric Sandeen <sandeen@sandeen.net>
To: xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfsprogs for-next updated to 4aaeedc4 / v5.9.0-rc1
Date: Tue, 13 Oct 2020 11:35:19 -0500 [thread overview]
Message-ID: <e4d9a624-7199-7d27-9c8d-7f66f27fbd2d@sandeen.net> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 2236 bytes --]
Hi folks,
The for-next branch of the xfsprogs repository at:
git://git.kernel.org/pub/scm/fs/xfs/xfsprogs-dev.git
has just been updated and tagged with v5.9.0-rc1.
Barring important missed patches or regressions, this will be the content
for v5.9.0 GA.
The new head of the for-next branch is commit:
b2fa3ec1 (HEAD -> for-next, korg/for-next, refs/patches/for-next/5.9.0-rc1.patch) xfsprogs: Release v5.9.0-rc1
New Commits:
Darrick J. Wong (4):
[0779e54d] libfrog: fix a potential null pointer dereference
[f4d02645] libhandle: fix potential unterminated string problem
[2b9857cd] xfs_scrub: don't use statvfs to collect filesystem summary counts
[86b8934d] xfs_repair: coordinate parallel updates to the rt bitmap
Eric Sandeen (2):
[b285432b] xfsprogs: fix ioctl_xfs_geometry manpage naming
[b2fa3ec1] xfsprogs: Release v5.9.0-rc1
Gao Xiang (1):
[8faa41b4] xfsprogs: allow i18n to xfs printk
Ian Kent (1):
[5ca4d781] xfsprogs: ignore autofs mount table entries
Code Diffstat:
VERSION | 2 +-
configure.ac | 2 +-
debian/changelog | 6 +++++
doc/CHANGES | 11 +++++++++
libfrog/bulkstat.c | 2 +-
libfrog/linux.c | 2 ++
libfrog/paths.c | 2 ++
libhandle/handle.c | 3 ++-
libxfs/libxfs_priv.h | 8 +++----
..._xfs_fsop_geometry.2 => ioctl_xfs_fsgeometry.2} | 10 ++++----
man/man3/xfsctl.3 | 4 ++--
repair/dinode.c | 16 ++++++-------
repair/globals.c | 1 +
repair/globals.h | 1 +
repair/incore.c | 1 +
scrub/fscounters.c | 27 ++++------------------
16 files changed, 52 insertions(+), 46 deletions(-)
rename man/man2/{ioctl_xfs_fsop_geometry.2 => ioctl_xfs_fsgeometry.2} (95%)
[-- Attachment #1.1.2: OpenPGP_0x20AE1692E13DDEE0.asc --]
[-- Type: application/pgp-keys, Size: 3947 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
reply other threads:[~2020-10-13 16:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e4d9a624-7199-7d27-9c8d-7f66f27fbd2d@sandeen.net \
--to=sandeen@sandeen.net \
--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;
as well as URLs for NNTP newsgroup(s).