From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Joe Perches <joe@perches.com>
Cc: akpm@linux-foundation.org, colin.king@canonical.com,
sfr@canb.auug.org.au, wangqing@vivo.com, david@redhat.com,
xndchn@gmail.com, luca@lucaceresoli.net, ebiggers@google.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] scripts: spelling: Remove space in the entry memry to memory
Date: Thu, 15 Oct 2020 19:24:07 +0530 [thread overview]
Message-ID: <20201015135407.GB1899805@ArchLinux> (raw)
In-Reply-To: <796974d4de89d1e8483d16f4f1f3d6324b49bf86.camel@perches.com>
[-- Attachment #1: Type: text/plain, Size: 587 bytes --]
On 06:38 Thu 15 Oct 2020, Joe Perches wrote:
>On Thu, 2020-10-15 at 18:53 +0530, Bhaskar Chowdhury wrote:
>> Fix the space in the middle in below entry.
>>
>> memry||memory
>[]
>> diff --git a/scripts/spelling.txt b/scripts/spelling.txt
>[]
>> @@ -885,7 +885,7 @@ meetign||meeting
>> memeory||memory
>> memmber||member
>> memoery||memory
>> -memry ||memory
>> +memry||memory
>
>No. Don't post a bad patch, assume
>it's applied and then post a fix to
>the bad patch as v2.
>
>Send a single clean patch.
>
Not sure what you mean...could you elaborate...don't know what is going on..>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-10-15 13:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 13:23 [PATCH V2] scripts: spelling: Remove space in the entry memry to memory Bhaskar Chowdhury
2020-10-15 13:38 ` Joe Perches
2020-10-15 13:54 ` Bhaskar Chowdhury [this message]
2020-10-15 21:10 ` Joe Perches
2020-10-15 22:49 ` Bhaskar Chowdhury
2020-10-15 22:53 ` Joe Perches
2020-10-15 22:55 ` Bhaskar Chowdhury
2020-10-15 23:06 ` Joe Perches
2020-10-15 23:08 ` Bhaskar Chowdhury
2020-10-16 3:19 ` Joe Perches
2020-10-16 3:49 ` Bhaskar Chowdhury
2020-10-16 8:10 ` David Hildenbrand
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=20201015135407.GB1899805@ArchLinux \
--to=unixbhaskar@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=colin.king@canonical.com \
--cc=david@redhat.com \
--cc=ebiggers@google.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@lucaceresoli.net \
--cc=sfr@canb.auug.org.au \
--cc=wangqing@vivo.com \
--cc=xndchn@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.