public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jules Maselbas <jmaselbas@kalray.eu>, linux-kernel@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: Fix repeated words in documentation
Date: Fri, 26 Aug 2022 19:45:00 +0700	[thread overview]
Message-ID: <70f2a63b-fe1b-34bd-a5fd-374e2628ee60@gmail.com> (raw)
In-Reply-To: <20220826095321.21548-1-jmaselbas@kalray.eu>

On 8/26/22 16:52, Jules Maselbas wrote:
> Remove redundant word `the`.
> 
What about "Remove duplicated 'the' across the whole documentation"
as patch subject and/or description?

This reminds me of typofix patch bombs from @cdjrlc.com people.

> -The arguments are the same as for the the cpuhp_state_add_instance*()
> +The arguments are the same as for the cpuhp_state_add_instance*()
>  variants above.
>  

The second 'the' isn't necessary.

Thanks.

-- 
An old man doll... just what I always wanted! - Clara

  reply	other threads:[~2022-08-26 12:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-26  9:52 [PATCH] Documentation: Fix repeated words in documentation Jules Maselbas
2022-08-26 12:45 ` Bagas Sanjaya [this message]
2022-08-26 14:33 ` [PATCH v2] Remove duplicated 'the' across the whole documentation Jules Maselbas
2022-08-26 15:47   ` Randy Dunlap
2022-08-26 16:34   ` [PATCH v3] Remove duplicated words " Jules Maselbas
2022-08-26 16:40     ` Conor.Dooley
2022-08-26 16:50       ` Jules Maselbas
2022-08-26 16:56     ` [PATCH v4] " Jules Maselbas
2022-08-26 23:06       ` Randy Dunlap
2022-08-29  9:26         ` Jules Maselbas
2022-08-29  9:29       ` [PATCH v5] " Jules Maselbas
2022-08-29 17:23         ` Conor Dooley
2022-08-29 18:58         ` Randy Dunlap
2022-08-29 16:30     ` [PATCH v3] " Jonathan Corbet

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=70f2a63b-fe1b-34bd-a5fd-374e2628ee60@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=corbet@lwn.net \
    --cc=jmaselbas@kalray.eu \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@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