From: Randy Dunlap <rdunlap@infradead.org>
To: Yash Suthar <yashsuthar983@gmail.com>, corbet@lwn.net
Cc: workflows@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Documentation/process: submitting-patches: fix typo in "were do"
Date: Sat, 20 Sep 2025 13:02:47 -0700 [thread overview]
Message-ID: <2456eb05-5697-4397-871c-cbc95bfab048@infradead.org> (raw)
In-Reply-To: <20250920190856.7394-1-yashsuthar983@gmail.com>
On 9/20/25 12:08 PM, Yash Suthar wrote:
> Fixes a typo in submitting-patches.rst:
> "were do" -> "where do"
>
> Signed-off-by: Yash Suthar <yashsuthar983@gmail.com>
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> v2: Resending patch as v1 received no reply. No code changes.
>
> Documentation/process/submitting-patches.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> index cede4e7b29af..fcc08eb93897 100644
> --- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -343,7 +343,7 @@ https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
> As is frequently quoted on the mailing list::
>
> A: http://en.wikipedia.org/wiki/Top_post
> - Q: Were do I find info about this thing called top-posting?
> + Q: Where do I find info about this thing called top-posting?
> A: Because it messes up the order in which people normally read text.
> Q: Why is top-posting such a bad thing?
> A: Top-posting.
--
~Randy
next prev parent reply other threads:[~2025-09-20 20:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-20 19:08 Yash Suthar
2025-09-20 20:02 ` Randy Dunlap [this message]
2025-09-21 22:34 ` 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=2456eb05-5697-4397-871c-cbc95bfab048@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=workflows@vger.kernel.org \
--cc=yashsuthar983@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