Re: [RFC PATCH] cmdline: Hide "debug" from /proc/cmdline

Diego Viola
2014-05-19T08:11:08Z

I mean "e.g.:" is wrong, it should be e.g. or e.g.,

Sorry to be too nitpicky or annoying about this.

Diego

On Mon, May 19, 2014 at 5:06 AM, Diego Viola <diego.viola@gmail.com> wrote:
> e.g. should be written as e.g. or e.g.,
>
> There's no need to add another colon ":" after the one that it's already there.
>
> See, http://en.wikipedia.org/wiki/E.g.#e.g.
>
> Please fix that.
>
> Thanks,
>
> Diego
>
> On Mon, May 5, 2014 at 9:57 PM, Rusty Russell <rusty@rustcorp.com.au> wrote:
>> Randy Dunlap <rdunlap@infradead.org> writes:
>>> All looks good to me except for 2 instances of "eg" which should be
>>> "e.g." (just above and about 4 paragraphs below here).
>>
>> Thanks, fixed:
>>
>> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
>> index 56a4c2d0c741..a42b9dd6b46b 100644
>> --- a/Documentation/kernel-parameters.txt
>> +++ b/Documentation/kernel-parameters.txt
>> @@ -14,7 +14,7 @@ environment, others are passed as command line arguments to init.
>> Everything after "--" is passed as an argument to init.
>>
>> Module parameters can be specified in two ways: via the kernel command
>> -line with a module name prefix, or via modprobe, eg:
>> +line with a module name prefix, or via modprobe, e.g.:
>>
>> (kernel command line) usbcore.blinkenlights=1
>> (modprobe command line) modprobe usbcore blinkenlights=1
>> @@ -30,7 +30,7 @@ Hyphens (dashes) and underscores are equivalent in parameter names, so
>> can also be entered as
>> log-buf-len=1M print_fatal_signals=1
>>
>> -Double-quotes can be used to protect spaces in values, eg:
>> +Double-quotes can be used to protect spaces in values, e.g.:
>> param="spaces in here"
>>
>> This document may not be entirely up to date and comprehensive. The command
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/