From: David Sterba <dsterba@suse.cz>
To: Zorro Lang <zlang@redhat.com>
Cc: Anand Jain <anand.jain@oracle.com>,
zlang@kernel.org, fstests@vger.kernel.org,
linux-btrfs@vger.kernel.org
Subject: Re: [GIT PULL] fstests: btrfs changes staged-20240418
Date: Wed, 24 Apr 2024 14:14:36 +0200 [thread overview]
Message-ID: <20240424121436.GK3492@twin.jikos.cz> (raw)
In-Reply-To: <20240424091243.72n37q2xlwf5hxky@dell-per750-06-vm-08.rhts.eng.pek2.redhat.com>
On Wed, Apr 24, 2024 at 05:12:43PM +0800, Zorro Lang wrote:
> On Wed, Apr 24, 2024 at 06:06:43AM +0800, Anand Jain wrote:
> > (I just realized that the previous attempt to send this PR failed. Resending it now.)
> >
> > Zorro,
> >
> > Several of the btrfs test cases were failing due to a change in the golden
> > output. The commits here fix them. These patches are on top of the last PR
> > branch staged-20240414.
>
> Hi Anand,
>
> I found lots of patches in this branch doesn't have RVB. That's not safe, if
> we always do things like that. We need one single peer review at least, that
> requirement is low enough I think.
>
> Better to ping btrfs-list or fstests-list or particular reviewers to get
> review, if some patches missed RVB.
Anand is maintainer within fstests and I guess he reviews the patches
when putting them to the branch for merge. Filipe is mentioned as
reviewer but please don't expect him to reivew each and every patch.
I have a feeling that you're following process of merging patches that
is maybe modeled after linux kernel, with the multiple branches and
even merge window (mentioned in previsous PR), but this is IMO
inadequate for a testsuite where we need quick fixups to test cases to
be released in a much shorter turnaround.
I was expecting that if there was a dedicated maintainer for a
filesystem then things would go smoothly and we could skip formalities
because the maintainer is expected to do reviews that count too.
next prev parent reply other threads:[~2024-04-24 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 22:06 [GIT PULL] fstests: btrfs changes staged-20240418 Anand Jain
2024-04-24 9:12 ` Zorro Lang
2024-04-24 12:14 ` David Sterba [this message]
2024-04-24 14:23 ` Zorro Lang
2024-04-24 15:49 ` Zorro Lang
2024-05-06 11:49 ` Anand Jain
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=20240424121436.GK3492@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@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