From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta1.migadu.com (out-27.mta1.migadu.com [95.215.58.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BA2503AF64F for ; Fri, 21 Aug 2026 13:12:01 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=95.215.58.27 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787317933; cv=none; b=lw+Jt8f4Uv277oa+q8E+Oi5uNbioq6RqaHHQUKE7fXvXj91k/nTY+JDanijnR71vLGRIMIAnk+iJaf80l+pIIPLwB5pHAnvbsxawhpQUIfffsaXmk1sikR7tE+ZSSRgFCGGNmZTUHUaqRdWCFi/mZ1fJUBSFrLuMOCMHfNgPigA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787317933; c=relaxed/simple; bh=CdQNugJKEYmxnAoz+nzLCPKFAwif5HJoUpmaDJJsK4g=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=pLSmQzGjl7RVdT4/qyGJRA9o8p7PPmzEBE8I+zcSoUoz9l2k/LetI4QNUihNJGkPTcbpI+HUb2FmD/9sZ42T0mFecOr11CAXqhBh+Ha67VpSPRCnZ6PeLgEJA3h4dcc2Drs8sxssyq1ZV8y6f7w2tJbsHovhC/RU4RLCxT3HqOk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=wyuan.org; spf=pass smtp.mailfrom=wyuan.org; dkim=pass (2048-bit key) header.d=wyuan.org header.i=@wyuan.org header.b=EuFFBUfu; arc=none smtp.client-ip=95.215.58.27 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=wyuan.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=wyuan.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=wyuan.org header.i=@wyuan.org header.b="EuFFBUfu" X-Envelope-To: linux-doc@vger.kernel.org DKIM-Signature: a=rsa-sha256; bh=CdQNugJKEYmxnAoz+nzLCPKFAwif5HJoUpmaDJJsK4g=; c=simple/simple; d=wyuan.org; h=from:to:subject:date:message-id:mime-version:content-type; s=key1; t=1787317918; v=1; x=1787922718; b=EuFFBUfuwqCT83uTLnbJlfILGmUFmuaD8fGKOX9L3ZRNCBGom1X2XmBjB6nQAvkHQdagS0DA Pk2z9uSzEbVKKCOgC55PGgD/GOTGKYDXKKKqjMn0Mjsa75HSD57jUWTbTQbFhUlIXTd7uIIwZxj 7PD0KmYAofbBtU7RuP9l7df8wewApXdBkgf1lC0ZKEsThCXzww2RpL4kfZXr9MgyByD6GkCDCAA vhxi07yIp8imjEuxKGscmlubfRFH21BDg0y1RNcBlpvrmKR9Ih+HBF6d35LGbL018hOKPcLYAqD sgVeokB9hkQEWSsLKg1X8GogP3mGnhfP81rF0c/V1uydw== X-Envelope-To: linux-doc@vger.kernel.org Received: from localhost (117.176.242.187) by smtp.migadu.com with ESMTPS id e287a48326585d31; Fri, 21 Aug 2026 13:11:48 +0000 X-Mizu-Trace-ID: e287a48326585d31 X-Migadu-Flow: FLOW_OUT Date: Fri, 21 Aug 2026 21:11:37 +0800 From: Weijie Yuan To: Dongliang Mu Cc: Alex Shi , Yanteng Si , Jonathan Corbet , Shuah Khan , Konstantin Ryabitsev , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/4] Update maintainer-pgp-guide.rst Chinese translation Message-ID: References: <20260821-maintainer-pgp-guide-v1-0-08e5e3602c04@wyuan.org> <5b107aad-2826-4bf6-97aa-14592131b6a8@hust.edu.cn> <7232a999-0bb8-45fa-8d33-a11efc661012@hust.edu.cn> <0e437b53-5a44-406f-a482-518a6c09f7e2@hust.edu.cn> <771c1b11-f7d3-4a1b-a26a-b20187eeae59@hust.edu.cn> Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <771c1b11-f7d3-4a1b-a26a-b20187eeae59@hust.edu.cn> On Fri, Aug 21, 2026 at 08:57:46PM +0800, Dongliang Mu wrote: > > On 8/21/26 8:48 PM, Weijie Yuan wrote: > > On Fri, Aug 21, 2026 at 08:17:06PM +0800, Dongliang Mu wrote: > > [...] > > > > (I definitely won't admit that the log file annoyed me a few times > > > > because I accidentally included it with 'git add .' and then had to 'git > > > > commit --amend' right after) ;-) > > > My experience is to not use 'git add .'. In Linux, hidden files are not > > > listed by default. > > Yes, I was being lazy to type the full pach/full file name, oops. > > > > While hidden files are not listed by default on Linux, thankfully the > > kernel source tree ignores .* via .gitignore. But 'git add .' is indeed > > a bad habit. > > > > Btw, git commit -v, or setting commit.verbose = true, can really save > > one at the last minute. (as mentioned in our how-to doc) And sadly I > > actually happened to use another computer to write patches last night, > > which I hadn't configured it. XD > > Actually these labor-tensive works should be done by LLM. This is one of the > right directions of LLM usage. > > You can write a simple skill to help you complete these works. That makes sense. I'll give it a try. Still, given that the kernel community tends to be a bit conservative, I've generally tried to do things myself. Of course, the most important thing is that we supervise what the LLM is doing and make sure it follows our actual intent rather than hallucinating. > > > > > > Btw I've been trying to know more about Sphinx and kernel-docs, hope my > > > > > > mistake won't happen again. > > > > > That change can fix problem. The underlying problem is RST syntax. Maybe you > > > > > can have a look at this or query it in the LLM. > > > > Absolutely. I did have relatively little experience writing rst before. > > > > But that's definitely no excuse - I'll try to pick it up quickly. > > > LLM is really useful to capture some syntax and semantics issues. Therefore, > > > before submitting patch, use LLM to scan problem in this issue. > > Got it, thanks. > > > > > I am writing a draft skill for reviewing patches of kernel Chinese > > > documentation. > > Nice! I've been trying "b4 review tui" these days and I also made some > > modifications to its pre-configured prompt to fit our specific > > workflows: > > > > https://git.kernel.org/pub/scm/utils/b4/b4.git/tree/misc/agent-reviewer.md > > > > b4 review tui 'agents' - AI-assisted review: > > > > https://b4.docs.kernel.org/en/latest/reviewer/getting-started.html#ai-assisted-review > > > > Sometimes my agent makes false alarms, but at other times it does manage > > to identify the issues that we have overlooked. This is probably also > > one of the reasons why the community is gradually becoming more > > accepting of LLMs. > > Ah, this is interesting. > > My skill is to use LLM to search the patch name, use b4 to apply patches and > finally ask LLM to refer to how-to.rst and review the patch or patchset. As Chen-Yu mentioned before, Iīve basically trained myself to find almost any email in the lore archives manually. ;-) And yes, every time before I send a patch, I have an LLM check whether it follows the instructions in the how-to.rst. > And I think we could try to add our subsystem to sashiko. What we need to do > is to write some subsystem-related prompts. I was thinking about this a few days ago. I'd actually planned to talk to the Sashiko maintainer about it first, but I havenīt gotten around to it yet. As far as I know, though, Sashiko can currently only be enabled based on mailing lists; it can't filter or match patches specifically for the Chinese translation subsystem. Overall, though, Iīm in favor of enabling Sashiko for us. Having an extra pair of automated eyes certainly doesn't hurt. That said, some settings may be worth discussing - for example, whether the Sashiko bot should be allowed to send review comments directly to the original patch thread. Thanks!