Incorrect Cc addresses in my recent emails

[Utkal Singh]

Hi Gao Xiang,

You are correct. I was careless in my previous email and apologized for a
patch that was not mine. I will be more precise in the future.

Regarding AI: I hear your concerns. I commit that I will not use AI to
write, generate, or suggest any patches or commit messages I submit. All
future work will be my own code and my own analysis.

I will also ensure that I use scripts/get_maintainer.pl and git send-email
correctly to avoid any further CC or formatting issues.

Best regards, Utkal Singh

On Thu, 19 Mar 2026 at 15:57, Gao Xiang <hsiangkao at linux.alibaba.com> wrote:

>
>
> On 2026/3/19 12:22, Utkal Singh wrote:
> > Hi Gao Xiang,
> >
> > I owe you and the list an apology.
> >
> > The incorrect Cc addresses in my recent emails (gaoxiang25 at kernel.org
> and
>
> Why "gaoxiang25 at kernel.org" was your fault?
>
> The patch with the incorrect "gaoxiang25 at kernel.org" Cc
> https://lore.kernel.org/r/20260316085300.19229-1-lasyaprathipati@gmail.com
>
> is not sent by you, correct?
>
> > yifan.yfzhao at linux.dev) were my fault. I used stale entries from Gmail
> > autocomplete without verifying them against lore.kernel.org or the
>
> I don't think Gmail web UI can send patches directly.
>
> > MAINTAINERS file. That was careless, and I understand why it raised
> > concerns.
> >
> > I have removed every stale address from my contacts. Going forward, I
> will
> > verify all recipients against get_maintainer.pl and the existing thread
> > headers on lore before every send.
> >
> > I also recognize that the volume of my patches over the past two weeks
> has
> > made your review work harder, not easier. I will slow down, consolidate
> > related fixes into proper series, and focus on quality over quantity.
> >
> > I appreciate the time you have spent reviewing my work, and I take your
> > feedback seriously.
>
> Please claim here that you are not using and will not using
> any AI to write patches in public, otherwise I will simply
> ignore your following patches unless your contribution is
> necessary to be fixed.
>
> Everyone can do vibe-coding (including me), I don't think
> it's fair that everyone throws "raw" patches made by AI to
> me and let me take my own time to review.
>
> Thanks,
> Gao Xiang
>
> >
> > Best regards,
> > Utkal Singh
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/linux-erofs/attachments/20260319/f30c3e24/attachment.htm>