public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Zorro Lang <zlang@redhat.com>
Cc: "Darrick J. Wong" <djwong@kernel.org>,
	Zorro Lang <zlang@kernel.org>,
	fstests@vger.kernel.org
Subject: Re: [ANNOUNCE] fstests: for-next branch updated to v2025.02.23
Date: Tue, 25 Feb 2025 09:04:25 +1100	[thread overview]
Message-ID: <Z7zs6bqldp38_5Sn@dread.disaster.area> (raw)
In-Reply-To: <20250224054839.zne2pykkrm2nll5d@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>

On Mon, Feb 24, 2025 at 01:48:39PM +0800, Zorro Lang wrote:
> On Sun, Feb 23, 2025 at 11:30:40AM -0800, Darrick J. Wong wrote:
> > On Sun, Feb 23, 2025 at 08:27:43PM +0800, Zorro Lang wrote:
> > > Hi all,
> > > 
> > > The for-next branch of the xfstests repository at:
> > > 
> > > 	git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
> > > 
> > > has just been updated and tagged as v2025.02.23 release.
> > > 
> > > Release Notes:
> > > 1) There's not new test cases in this release, this's a release for bug fixes
> > >    particularly.
> > > 2) Reiserfs part is removed from fstests.
> > > 3) ltp/growfiles is removed too, I think no one needs it.
> > > 
> > > I can't list all updates at here, more details please refer to below.
> > > Thanks for all these contributions!
> > 
> > Thanks, Zorro.  I know the last few months have been rough. :/
> 
> Thank *you* help a lot, and always be patiented to take review points to
> your patchset, finally we got these patches in :)
> 
> Next, I'm going to deal with your 10 PRs (73 patches), and another patchset
> about the check-parallel ([PATCH 0/5]: CLI and feature improvements for
> check-parallel). Will talk details with you after my testing.

No, please do not pull those check-parallel patches or waste time
trying to apply/review them right now. I have rebased and updated
versions locally that I'm getting ready to send out - this has been
waiting on Darrick's namespace helper fixes to land so I can test
things with those patches in place...

-Dave.
-- 
Dave Chinner
david@fromorbit.com

  reply	other threads:[~2025-02-24 22:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-23 12:27 [ANNOUNCE] fstests: for-next branch updated to v2025.02.23 Zorro Lang
2025-02-23 19:30 ` Darrick J. Wong
2025-02-24  5:48   ` Zorro Lang
2025-02-24 22:04     ` Dave Chinner [this message]
2025-02-25  9:00       ` Zorro Lang
2025-02-28 12:33 ` David Sterba
2025-02-28 17:33   ` Darrick J. Wong
2025-03-01  1:01     ` Theodore Ts'o
2025-03-01 14:08   ` Zorro Lang
2025-03-02 13:13     ` Filipe Manana
2025-03-02 14:50       ` Theodore Ts'o
2025-03-02 16:18         ` Zorro Lang
2025-03-02 18:42         ` Filipe Manana
2025-03-02 15:37       ` Zorro Lang
2025-03-02 19:02         ` Filipe Manana
2025-03-02 19:56           ` Zorro Lang
2025-03-01 16:50   ` Zorro Lang
2025-03-04 18:58     ` Darrick J. Wong
     [not found] <67bb1448.500a0220.af3ac.9928SMTPIN_ADDED_BROKEN@mx.google.com>
2025-02-27 13:32 ` Filipe Manana
2025-02-27 17:52   ` Darrick J. Wong
2025-02-28 11:54     ` David Sterba
2025-03-01 17:22   ` Zorro Lang
2025-03-04 18:37     ` 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=Z7zs6bqldp38_5Sn@dread.disaster.area \
    --to=david@fromorbit.com \
    --cc=djwong@kernel.org \
    --cc=fstests@vger.kernel.org \
    --cc=zlang@kernel.org \
    --cc=zlang@redhat.com \
    /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