Linux Documentation
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Dongliang Mu <dzm91@hust.edu.cn>
Cc: Alex Shi <alexs@kernel.org>, Yanteng Si <si.yanteng@linux.dev>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] Update maintainer-pgp-guide.rst Chinese translation
Date: Fri, 21 Aug 2026 20:48:44 +0800	[thread overview]
Message-ID: <aohJLNK5Cqv1iMLd@wyuan.org> (raw)
In-Reply-To: <0e437b53-5a44-406f-a482-518a6c09f7e2@hust.edu.cn>

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

[...]
> > > > 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.

Thanks!

  reply	other threads:[~2026-08-21 12:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 17:13 [PATCH 0/4] Update maintainer-pgp-guide.rst Chinese translation Weijie Yuan
2026-08-20 17:13 ` [PATCH 1/4] docs/zh_CN: update maintainer-pgp-guide translation Weijie Yuan
2026-08-20 17:13 ` [PATCH 2/4] docs/zh_CN: clarify free Nitrokey requirements Weijie Yuan
2026-08-20 17:13 ` [PATCH 3/4] docs/zh_CN: update maintainer-pgp-guide kernel.org link Weijie Yuan
2026-08-20 17:13 ` [PATCH 4/4] docs/zh_CN: add kernel.org trust repository reference Weijie Yuan
2026-08-20 17:38   ` Weijie Yuan
2026-08-21  4:14     ` Dongliang Mu
2026-08-21  5:14       ` Weijie Yuan
2026-08-21  6:54 ` [PATCH 0/4] Update maintainer-pgp-guide.rst Chinese translation Dongliang Mu
2026-08-21  7:22   ` Weijie Yuan
2026-08-21 11:18     ` Dongliang Mu
2026-08-21 11:56       ` Weijie Yuan
2026-08-21 12:17         ` Dongliang Mu
2026-08-21 12:48           ` Weijie Yuan [this message]
2026-08-21 12:57             ` Dongliang Mu
2026-08-21 13:11               ` Weijie Yuan
2026-08-21 13:45                 ` Dongliang Mu
2026-08-21 14:01                   ` Weijie Yuan

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=aohJLNK5Cqv1iMLd@wyuan.org \
    --to=wy@wyuan.org \
    --cc=alexs@kernel.org \
    --cc=corbet@lwn.net \
    --cc=dzm91@hust.edu.cn \
    --cc=konstantin@linuxfoundation.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=si.yanteng@linux.dev \
    --cc=skhan@linuxfoundation.org \
    /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