From: Randy Dunlap <randy.dunlap@oracle.com>
To: Lucas De Marchi <lucas.de.marchi@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Fix typos
Date: Thu, 02 Sep 2010 13:00:38 -0700 [thread overview]
Message-ID: <4C800266.1000005@oracle.com> (raw)
In-Reply-To: <AANLkTinehv75C+xhsDA_7HHoT9m_BkmL1aE_oyM9BJO4@mail.gmail.com>
On 09/02/10 12:31, Lucas De Marchi wrote:
> On Thu, Sep 2, 2010 at 16:18, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>> Hi,
>>
>> I'd take most of the corrections in Documentation/, but in general,
>> I don't think that it's a good idea without some careful review.
>
> I plan to review it if it's indeed worth fixing those typos. I already
> fixed several false positives like "rela" being changed to "real",
> but since it's a 1.8 MB patch I think it's better to ask first before
> making any other review.
>
>>
>> E.g.:
>>
>> 1. changing thru to through isn't needed IMO.
>> Can you add "thru" to your dictionary?
> Yes, no problem
>
>>
>> 2.
>> -(Warning, pulses on ACK ar inverted by transistor, irq is rised up on sync
>> +(Warning, pulses on ACK ar inverted by transistor, irq is rose up on sync
>>
> Humn.. indeed this seems to be a bad typo in my dictionary.
>
>> I'm not so sure about "is rose up" being better. and what about "ar"?
>
> I'm only changing words with 3 chars or more, because otherwise I
> would have a lot of false positives, but I think I can add this word
> without much trouble.
>
Mike's suggested change is good here.
>>
>> I saw a few others that I could comment on, but I lost them in the 1.8 MB patch file.
>
> If you say it's good, I can review it more carefully.
It looks good for Documentation/.
And fixing typos is certainly something that we want to do in
user-visible messages, like printk strings.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-09-02 20:01 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-02 19:05 [RFC] Fix typos Lucas De Marchi
2010-09-02 19:18 ` Randy Dunlap
2010-09-02 19:31 ` Lucas De Marchi
2010-09-02 20:00 ` Randy Dunlap [this message]
2010-09-02 20:08 ` Lucas De Marchi
2010-09-02 20:13 ` Randy Dunlap
2010-09-02 20:47 ` Lucas De Marchi
2010-09-02 20:16 ` Mike Frysinger
2010-09-02 20:23 ` Lucas De Marchi
2010-09-02 20:25 ` Randy Dunlap
2010-09-02 20:45 ` Lucas De Marchi
2010-09-03 2:29 ` Phillip Lougher
2010-09-03 2:45 ` Lucas De Marchi
2010-09-03 5:20 ` Lucas De Marchi
2010-09-03 5:23 ` Lucas De Marchi
2010-09-02 19:32 ` Mike Frysinger
2010-09-03 2:17 ` Phillip Lougher
2010-09-07 16:06 ` Paul E. McKenney
2010-09-07 16:47 ` Len Brown
2010-09-07 17:01 ` Lucas De Marchi
2010-09-07 17:30 ` Jason Wessel
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=4C800266.1000005@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.de.marchi@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