From: Christoph Hellwig <hch@infradead.org>
To: David Sterba <dsterba@suse.cz>
Cc: Zorro Lang <zlang@redhat.com>, Anand Jain <anand.jain@oracle.com>,
fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [GIT PULL] fstests: btrfs changes for for-next staged-20250328
Date: Thu, 3 Apr 2025 23:11:57 -0700 [thread overview]
Message-ID: <Z-94LaTObhgZT2Rq@infradead.org> (raw)
In-Reply-To: <20250328180213.GH32661@twin.jikos.cz>
On Fri, Mar 28, 2025 at 07:02:13PM +0100, David Sterba wrote:
> Maintainers should be allowed to push their patches without RVB, that's
> where the role and status adds value.
Hell no. Stop beeing so weirdly entitlted, that absolutely does not
help to get you anywhere. If you are so proud of your role and status
use that to nudge someone into reviewing the patches insted.
Why the f**k do we wven have to discuss these basics?
prev parent reply other threads:[~2025-04-04 6:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 1:26 [GIT PULL] fstests: btrfs changes for for-next staged-20250328 Anand Jain
2025-03-28 2:03 ` Zorro Lang
2025-03-28 2:53 ` Anand Jain
2025-03-28 18:02 ` David Sterba
2025-04-04 6:11 ` Christoph Hellwig [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=Z-94LaTObhgZT2Rq@infradead.org \
--to=hch@infradead.org \
--cc=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.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