mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Weijie Yuan <wy@wyuan.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Nguyen Duc Thinh <ducthinh100812@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	Randy Dunlap <rdunlap@infradead.org>,
	workflows@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/5] Documentation: process: Clean up grammar, tone,
Date: Fri, 4 Sep 2026 01:26:26 +0800	[thread overview]
Message-ID: <apmtwqxrkg8pN0aL@wyuan.org> (raw)
In-Reply-To: <20260903125454.GA541154@killaraus.ideasonboard.com>

On Thu, Sep 03, 2026 at 03:54:54PM +0300, Laurent Pinchart wrote:
> > On Wed, Sep 02, 2026 at 03:43:58PM +0700, Nguyen Duc Thinh wrote:
> > > This patch series performs a thorough pass across several files 
> > > in the Linux kernel process documentation directory. The primary focus
> > > is to improve readability and maintain a professional tone throughout 
> > > the guides for a global developer audience.
> > > 
> > > Core changes include:
> > > - Expanding conversational contractions (e.g., "don't" to "do not").
> > 
> > Is this necessary? I'm not sure.
> 
> It seems a bit pointless to me. Contractions will creep back in as
> patches are merged. We would need e documentation editor in charge of
> ensuring a consistent style, and I think the documentation maintainers
> have far better things to do.

Agreed. I think contractions are fine as they are. (?) And I do not see
a need to expand them.

> > > - Rectifying minor punctuation oversights and grammatical typos.
> > > - Standardizing terminology formatting to elevate professional voice.

For these two points, it's a little bit painful to find other types of
modifications among numerous "which/that". ;-)

Thanks.

  reply	other threads:[~2026-09-03 17:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02  8:43 Nguyen Duc Thinh
2026-09-02  8:43 ` [PATCH v2 1/5] Documentation: process: Clean up grammar, tone, and contractions in core files Nguyen Duc Thinh
2026-09-02  8:44 ` [PATCH v2 2/5] Documentation: process: Clean up grammar and tone in next guide files Nguyen Duc Thinh
2026-09-02  8:44 ` [PATCH v2 3/5] Documentation: process: Refine language, tone, and grammar in subsequent files Nguyen Duc Thinh
2026-09-02  8:44 ` [PATCH v2 4/5] " Nguyen Duc Thinh
2026-09-02  8:44 ` [PATCH v2 5/5] Documentation: process: Clean up grammar and tone across multiple files Nguyen Duc Thinh
2026-09-03 12:29 ` [PATCH v2 0/5] Documentation: process: Clean up grammar, tone, Weijie Yuan
2026-09-03 12:54   ` Laurent Pinchart
2026-09-03 17:26     ` Weijie Yuan [this message]
2026-09-03 17:39       ` Jonathan Corbet
2026-09-03 16:33   ` Randy Dunlap
2026-09-03 16:55     ` Weijie Yuan
  -- strict thread matches above, loose matches on Subject: below --
2026-09-02  8:43 Nguyen Duc Thinh
2026-09-02 19:17 ` Randy Dunlap

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=apmtwqxrkg8pN0aL@wyuan.org \
    --to=wy@wyuan.org \
    --cc=corbet@lwn.net \
    --cc=ducthinh100812@gmail.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.org \
    --cc=workflows@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

all inboxes | Powered by JetHome®