From: Gabriele Monaco <gmonaco@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
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, 04 Jun 2026 15:04:47 +0200 [thread overview]
Message-ID: <1ec107781373557924ee369ee13bf69d1efaa12c.camel@redhat.com> (raw)
In-Reply-To: <20260604085405.234d22eb@fedora>
On Thu, 2026-06-04 at 08:54 -0400, Steven Rostedt wrote:
> 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.
Alright, fair. In the link I sent, the signoff got changed to Ali Ahmet
MEMIS <dev@unknownbbqr.xyz>, but I believe we cannot use that unless
the user themselves adds it (and they seem unreachable).
I posted the re-authored patch in [1], I'm not sure that's the proper
way though (the patch is so simple that is unmodified). But if you give
me a green light I can send you a pull request with that patch instead.
Thanks,
Gabriele
[1] -
https://lore.kernel.org/lkml/20260604120946.90302-2-gmonaco@redhat.com/
>
> -- Steve
next prev parent reply other threads:[~2026-06-04 13:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 12:50 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
2026-06-04 13:04 ` Gabriele Monaco [this message]
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=1ec107781373557924ee369ee13bf69d1efaa12c.camel@redhat.com \
--to=gmonaco@redhat.com \
--cc=dev@unknownbbqr.xyz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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
Powered by JetHome