From: Eric Sandeen <sandeen@sandeen.net>
To: linux-xfs <linux-xfs@vger.kernel.org>
Subject: [ANNOUNCE] xfsprogs for-next updated to bf297b1
Date: Thu, 5 Jul 2018 15:33:17 -0500 [thread overview]
Message-ID: <c70d00b8-c754-166f-1f07-37cbeea4e7c7@sandeen.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1645 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.
This is really only the libxfs sync, so no need to panic if your patches
are not yet included.
The new head of the for-next branch is commit:
bf297b1 xfsprogs: Release v4.18.0-rc0
Note:
I've decided to start tagging things with -rc0 once the majority of libxfs
is synced up after the previous point release so that tarballs, packages, etc
have a version newer than the last point release. It was confusing and a
hassle to be creating "4.17.0" tarballs well past the 4.17.0 point release.
If this bothers people let me know, for-next is still malleable. ;)
New Commits:
Darrick J. Wong (3):
[5b50159] xfs: don't allow insert-range to shift extents past the maximum
[a4b61d9] xfs: fix off-by-one error in xfs_rtalloc_query_range
[2d49506] xfs: fix fdblocks accounting w/ RMAPBT per-AG reservation
Dave Chinner (1):
[8ac50ba] xfs: More robust inode extent count validation
Eric Sandeen (1):
[bf297b1] xfsprogs: Release v4.18.0-rc0
Code Diffstat:
VERSION | 4 +--
configure.ac | 2 +-
debian/changelog | 7 +++++
doc/CHANGES | 3 ++
libxfs/xfs_ag_resv.c | 31 +++++++++++++++++---
libxfs/xfs_bmap.c | 26 +++++++++++++++++
libxfs/xfs_bmap.h | 2 ++
libxfs/xfs_format.h | 5 ++++
libxfs/xfs_inode_buf.c | 76 +++++++++++++++++++++++++++++++-------------------
libxfs/xfs_rtbitmap.c | 4 +--
10 files changed, 122 insertions(+), 38 deletions(-)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 873 bytes --]
reply other threads:[~2018-07-05 20:33 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=c70d00b8-c754-166f-1f07-37cbeea4e7c7@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).