<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Vishwakarma,</p>
<p><br>
</p>
<p><span
style="color: rgb(29, 29, 31); font-family: system-ui, ui-sans-serif, -apple-system, BlinkMacSystemFont, Inter, NotoSansHans, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: pre-line; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">Just a quick note for you and all the beginning committers:</span></p>
<p><span
style="color: rgb(29, 29, 31); font-family: system-ui, ui-sans-serif, -apple-system, BlinkMacSystemFont, Inter, NotoSansHans, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: pre-line; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">Before submitting any patch to our community mailing list, please carefully read the contribution guidelines (we follow the Linux kernel process: [1]).</span></p>
<p><span
style="color: rgb(29, 29, 31); font-family: system-ui, ui-sans-serif, -apple-system, BlinkMacSystemFont, Inter, NotoSansHans, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: pre-line; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">You're welcome to use AI agents to help check whether the patch obeys the guidelines, but please remember to personally review your changes, test locally, and understand what you're submitting.</span></p>
<p><br>
</p>
<p>Also we are about to <span
style="color: rgb(29, 29, 31); font-family: system-ui, ui-sans-serif, -apple-system, BlinkMacSystemFont, Inter, NotoSansHans, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: pre-line; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">publish specific guidelines for AI-assisted content.</span></p>
<p><br>
</p>
<p><span
style="color: rgb(29, 29, 31); font-family: system-ui, ui-sans-serif, -apple-system, BlinkMacSystemFont, Inter, NotoSansHans, sans-serif; font-size: 16px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: pre-line; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; display: inline !important; float: none;">Finally, before sending any email to the mailing list, we strongly recommend sending a test to your own inbox first—messages posted to the list are permanent and cannot be edited or retracted.</span></p>
<p><br>
</p>
<p>[1] <a class="moz-txt-link-freetext" href="https://docs.kernel.org/process/submitting-patches.html">https://docs.kernel.org/process/submitting-patches.html</a></p>
<p>[ This email is generated with help with Qwen3.5-plus:
translation from Chinese to English ]</p>
<p><br>
</p>
<p>Thanks,</p>
<p>Yifan Zhao</p>
<p><br>
</p>
<div class="moz-cite-prefix">On 2026/3/20 10:04, Shubham Vishwakarma
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAPs1YC4Us+bPMKsGAUywWcp5sWzvTX6D-+naVz1y3M6F-iwXwA@mail.gmail.com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Hi Gao,</div>
<div><br>
</div>
<div>I understand the concern, but I want to be honest: if I had
used AI to draft the initial submission, it likely would have
been sent without those formatting errors.</div>
<div><br>
</div>
<div>The issues with the invalid email address and the oversized
subject line occurred because I was unfamiliar with sending
via the SMTP CLI. I used GPT to help me configure the CLI
tool, which led to the mistakes you saw.</div>
<div><br>
</div>
<div>I appreciate the feedback on the patch. If there is still
doubt regarding my work, I will continue to submit more
patches to demonstrate my ability.</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Shubham Vishwakarma</div>
<br>
</div>
<br>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr" class="gmail_attr">On Fri, Mar 20, 2026 at
7:11 AM Gao Xiang <<a
href="mailto:hsiangkao@linux.alibaba.com"
moz-do-not-send="true" class="moz-txt-link-freetext">hsiangkao@linux.alibaba.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
<br>
On 2026/3/20 09:37, Gao Xiang wrote:<br>
> <br>
> <br>
> On 2026/3/20 09:16, Ajay Rajera wrote:<br>
>> Hi Vi-shub,<br>
>> just a review :<br>
>> I think the fix looks correct and it is the right
approach but the<br>
>> commit message formatting needs work. The entire
description is in the<br>
>> subject line. Per kernel conventions, the subject
should be a short<br>
>> one-liner, e.g: erofs-utils: lib: fix QPL job leak on
early error<br>
>> paths<br>
>> The detailed explanation (which error paths leak,
why, and how the fix<br>
>> works) should go in the commit message body,
separated from the<br>
>> subject.<br>
>><br>
>> So you can resend with the subject/body split fixed?
so It will look more clear.<br>
> <br>
> yes, the commit message is in a mess.<br>
<br>
BTW, I don't know who is using the email address<br>
<<a href="mailto:yifan@pku.edu.cn" target="_blank"
moz-do-not-send="true" class="moz-txt-link-freetext">yifan@pku.edu.cn</a>>,
and the recipient doesn't exist.<br>
<br>
Here, I want to say, I have to identfy you as another<br>
AI bot.<br>
<br>
Thanks,<br>
Gao Xiang<br>
<br>
> <br>
> Thanks,<br>
> Gao Xiang<br>
> <br>
>> Thanks, Ajay<br>
> <br>
<br>
</blockquote>
</div>
</blockquote>
</body>
</html>