From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Matthew Wilcox <willy@infradead.org>,
sir@cmpwn.com, gregkh@linuxfoundation.org, lee.jones@linaro.org,
bp@alien8.de, huawei@kernel.org, krzk@kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
rdunlap@infradead.org
Subject: Re: [PATCH] docs: submitting-patches Fix a typo
Date: Tue, 23 Mar 2021 01:36:11 +0530 [thread overview]
Message-ID: <YFj4s6ZPh2QFd9oS@ArchLinux> (raw)
In-Reply-To: <87ft0nl31i.fsf@meer.lwn.net>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
On 07:40 Mon 22 Mar 2021, Jonathan Corbet wrote:
>Bhaskar Chowdhury <unixbhaskar@gmail.com> writes:
>
>> On 03:44 Mon 22 Mar 2021, Matthew Wilcox wrote:
>>>On Mon, Mar 22, 2021 at 09:00:00AM +0530, Bhaskar Chowdhury wrote:
>>>>
>>>> s/mesages/messages/
>>>
>>>did you test the build afterwards? you forgot to do something.
>>>
>> What are you talking about??? It is going over my head...why the build
>> reqired?? A spello needs a rebuild???? Wondering....
>
>Willy is pointing out that you have introduced an error into the docs
>build. A few minutes of your time to learn the basics of RST are likely
>to prove more helpful then typing lots of question marks...
>
Meh ...wish people learn to more explicit be in the first place ..heck..
>Thanks,
>
>jon
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2021-03-22 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 3:30 [PATCH] docs: submitting-patches Fix a typo Bhaskar Chowdhury
2021-03-22 3:44 ` Matthew Wilcox
2021-03-22 3:48 ` Bhaskar Chowdhury
2021-03-22 4:02 ` Matthew Wilcox
2021-03-22 4:16 ` Bhaskar Chowdhury
2021-03-22 13:40 ` Jonathan Corbet
2021-03-22 20:06 ` Bhaskar Chowdhury [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=YFj4s6ZPh2QFd9oS@ArchLinux \
--to=unixbhaskar@gmail.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=huawei@kernel.org \
--cc=krzk@kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sir@cmpwn.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).