mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] tracing: fix spelling mistakes
Date: Sat, 29 May 2021 10:40:27 +0800	[thread overview]
Message-ID: <f2004397-4b3f-2f94-dc12-09b95930db1c@huawei.com> (raw)
In-Reply-To: <20210528221113.4f66aaea@oasis.local.home>



On 2021/5/29 10:11, Steven Rostedt wrote:
> On Sat, 29 May 2021 10:01:31 +0800
> "Leizhen (ThunderTown)" <thunder.leizhen@huawei.com> wrote:
> 
>> On 2021/5/29 9:13, Steven Rostedt wrote:
>>> On Tue, 25 May 2021 14:20:47 +0800
>>> Zhen Lei <thunder.leizhen@huawei.com> wrote:
>>>   
>>>> Fix some spelling mistakes in comments:
>>>> wont ==> won't  
>>>
>>> I prefer not to fix that spelling. I sometimes purposely leave off
>>> single quotes. It's no that big of a deal, and doesn't deserve the
>>> churn.  
>>
>> Yes, all people can get it right by their wits. "Wont" doesn't affect
>> their reading speed. But most people might think it's best to add the
>> missing single quote.
>>
>> The minority obeys the majority?
> 
> I really don't care. In my opinion, it's unnecessary churn, that just
> adds noise to the git logs.

git grep -wn wont | wc -l
83

OK, I just did a search for "wont", and there are currently 83 places in
use. Language is not mathematics, there is no absolute right or wrong. If
a lot of people are using it incorrectly or specifically, then the new one
is also right.

Wow, should I send v2 to remove "wont ==> won't"?

> 
> -- Steve
> 
> .
> 


  reply	other threads:[~2021-05-29  2:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25  6:20 [PATCH 0/1] " Zhen Lei
2021-05-25  6:20 ` [PATCH 1/1] " Zhen Lei
2021-05-29  1:13   ` Steven Rostedt
2021-05-29  2:01     ` Leizhen (ThunderTown)
2021-05-29  2:11       ` Steven Rostedt
2021-05-29  2:40         ` Leizhen (ThunderTown) [this message]
2021-05-29  3:03           ` Leizhen (ThunderTown)
2021-06-16 12:12         ` Leizhen (ThunderTown)

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=f2004397-4b3f-2f94-dc12-09b95930db1c@huawei.com \
    --to=thunder.leizhen@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.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®