From: Steven Rostedt <rostedt@goodmis.org>
To: Gabriele Monaco <gmonaco@redhat.com>
Cc: Tomas Glozar <tglozar@redhat.com>,
linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
unknownbbqrx <dev@unknownbbqr.xyz>, Wen Yang <wen.yang@linux.dev>
Subject: Re: [GIT PULL] rv fixes for v7.1
Date: Thu, 4 Jun 2026 08:54:05 -0400 [thread overview]
Message-ID: <20260604085405.234d22eb@fedora> (raw)
In-Reply-To: <791528a4f69460ba1e9589361860bafeb1517237.camel@redhat.com>
On Thu, 04 Jun 2026 14:42:02 +0200
Gabriele Monaco <gmonaco@redhat.com> wrote:
> All this to say that, in my opinion unknownbbqrx <dev@unknownbbqr.xyz>
> is NOT an anonymous contribution, just a nickname that differs from the
> legal name of this person (which we wouldn't validate anyway), so I
> would say it complies with the rules.
It's a username on github and not a nickname. I did a search for
"unknownbbqr" and it doesn't come up anywhere but Google tries to find
similar matches which brings me to an OnlyFans account :-p
It *DOES NOT* qualify because there's no accountability for this. For
people who have a nickname as their entire internet persona, sure, I'll
take patches from them as there's an entity that exists behind it. But
I'm not going to take some username on github as a persona. To me,
that's still anonymous.
-- Steve
next prev parent reply other threads:[~2026-06-04 12:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 12:50 [GIT PULL] rv fixes for v7.1 Gabriele Monaco
2026-06-03 23:16 ` Steven Rostedt
2026-06-04 11:32 ` Tomas Glozar
2026-06-04 12:42 ` Gabriele Monaco
2026-06-04 12:54 ` Steven Rostedt [this message]
2026-06-04 13:04 ` Gabriele Monaco
2026-06-04 12:44 ` Steven Rostedt
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=20260604085405.234d22eb@fedora \
--to=rostedt@goodmis.org \
--cc=dev@unknownbbqr.xyz \
--cc=gmonaco@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=tglozar@redhat.com \
--cc=wen.yang@linux.dev \
/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