From: "Darrick J. Wong" <djwong@kernel.org>
To: Carlos Maiolino <carlos@maiolino.me>
Cc: linux-xfs@vger.kernel.org
Subject: Re: [ANNOUNCE] xfsprogs: for-next updated to d5d677df7
Date: Tue, 23 Apr 2024 20:22:55 -0700 [thread overview]
Message-ID: <20240424032255.GD360919@frogsfrogsfrogs> (raw)
In-Reply-To: <6edmi2wfmto4sbw4miohlhfvbiyhg5hdan52dk27canoug6425@6c4acq6bzngn>
On Tue, Apr 23, 2024 at 02:42:05PM +0000, Carlos Maiolino wrote:
> 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:
>
> d5d677df76af140532dc95f8fb133ba340ea64c8
>
> 118 new commits:
<snip>
> [164a5514c] xfs_repair: push inode buf and dinode pointers all the way to inode fork processing
> [e88445180] xfs_repair: sync bulkload data structures with kernel newbt code
> [b3bcb8f0a] xfs_repair: rebuild block mappings from rmapbt data
Heya, the first non-experimental user of the rmap btree data!
Thanks for merging this :)
--D
prev parent reply other threads:[~2024-04-24 3:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 14:42 [ANNOUNCE] xfsprogs: for-next updated to d5d677df7 Carlos Maiolino
2024-04-24 3:22 ` Darrick J. Wong [this message]
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=20240424032255.GD360919@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=carlos@maiolino.me \
--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 read-only IMAP folder(s) and NNTP newsgroup(s).