From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] man7, man2: document SCHED_EXT policy
Date: Wed, 22 Apr 2026 18:59:01 +0200 [thread overview]
Message-ID: <aej9PG3FsVRGaR3W@devuan> (raw)
In-Reply-To: <20260422163603.xvgyqulnl7knxeem@illithid>
[-- Attachment #1: Type: text/plain, Size: 2124 bytes --]
Hi Branden,
On 2026-04-22T11:36:03-0500, G. Branden Robinson wrote:
> [stripping distribution down to just the linux-man list and Alex]
>
> At 2026-04-23T00:13:57+0800, Cheng-Yang Chou wrote:
> > On Wed, Apr 22, 2026 at 06:02:49PM +0200, Alejandro Colomar wrote:
> > > > @@ -218,8 +223,10 @@ This field specifies the nice value to be set when specifying
> > > > .I sched_policy
> > > > as
> > > > .B SCHED_OTHER
> > > > +,
> > >
> > > What's the reason for this weird formatting of the source code? At
> > > this point I wonder if this was generated by AI.
> >
> > Yes, I used AI for the formatting, which I should disclose it, hence
> > the weird layout.
>
> I don't know, man, I stuck a comma on a line by itself in a man page
> just the other day. ;-)
I've seen several other clues in the patch. This was the once that
confirmed it to me. At first I thought that maybe the contributor could
not know that BR exists, and thus try that naively (I've seen that done
in other patches). However, 2 lines below there the patch introduced
a line using BR perfectly. That very much read like random LLM stuff.
There was also the arbitrary combined use of .P and .PP. I suspect no
human would use both in a document, unless the surrounding style already
uses both (which could confuse). Since we only have .P, the .PP came
out of nowhere.
And then there's the extensive use of \f (without brackets) and \(bu, of
which we have no cases anymore.
All of this was very suspicious, so I had to ask.
Have a lovely day!
Alex
>
> https://lists.gnu.org/archive/html/groff-commit/2026-04/msg00282.html
>
> +We prefix macro names with
> +_ifstyle()dnl
> +a dot
> +.RB ( . ),
> +_endif()dnl
> +the default
> +.I roff
> +control character\c
> +_ifstyle()dnl
> +,
> +_endif()dnl
> +_ifnotstyle()dnl
> +\&
> +_endif()dnl
> +in summaries and synopses.
>
> (Lest anyone hyperventilate, that's not a man(7) document per se, but an
> m4(1) document that _generates_ a man(7) document.)
>
> Regards,
> Branden
--
<https://www.alejandro-colomar.es>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-04-22 16:59 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 [this message]
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
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=aej9PG3FsVRGaR3W@devuan \
--to=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.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