From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Cheng-Yang Chou <yphbchou0911@gmail.com>
Cc: Alejandro Colomar <alx@kernel.org>, linux-man@vger.kernel.org
Subject: Re: [PATCH] man7, man2: document SCHED_EXT policy
Date: Wed, 22 Apr 2026 12:04:57 -0500 [thread overview]
Message-ID: <20260422170457.llynbvayfrtilnpp@illithid> (raw)
In-Reply-To: <20260423003214.G1987@cchengyang.duckdns.org>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
Hi Cheng-Yang,
At 2026-04-23T00:46:44+0800, Cheng-Yang Chou wrote:
> On Wed, Apr 22, 2026 at 06:02:49PM +0200, Alejandro Colomar wrote:
> > What's the reason for this weird formatting of the source code? At
> > this point I wonder if this was generated by AI.
> >
> > Please take into account 'CONTRIBUTING.d/ai'.
>
> Okay, after reading the AI policy doc carefully, I've decided to drop
> this patch. I used AI to help with the formatting since I'm not
> familiar with the rules here.
I urge you not to give up easily. The man(7) language is not hard to
acquire, and the more you stick to time-tested idioms the easier it
gets. Here's a guide I wrote over 20 years ago.
https://web.archive.org/web/20060102165607/http://people.debian.org/~branden/talks/wtfm/wtfm.pdf
I standy by most of it, notably excepting my spelling of "manpages" as
one word. Oh, to be so young and callow again... ;-)
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2026-04-22 17:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-12 18:16 [PATCH] man7, man2: document SCHED_EXT policy Cheng-Yang Chou
2026-04-22 16:02 ` Alejandro Colomar
2026-04-22 16:13 ` Cheng-Yang Chou
2026-04-22 16:36 ` G. Branden Robinson
2026-04-22 16:59 ` Alejandro Colomar
2026-04-22 17:23 ` G. Branden Robinson
2026-04-22 18:08 ` Alejandro Colomar
2026-04-22 16:46 ` Cheng-Yang Chou
2026-04-22 17:04 ` Alejandro Colomar
2026-04-22 17:04 ` G. Branden Robinson [this message]
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=20260422170457.llynbvayfrtilnpp@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=yphbchou0911@gmail.com \
/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