From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754940AbaESOlR (ORCPT ); Mon, 19 May 2014 10:41:17 -0400 Received: from merlin.infradead.org ([205.233.59.134]:48339 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754392AbaESOlP (ORCPT ); Mon, 19 May 2014 10:41:15 -0400 Message-ID: <537A17F8.6050109@infradead.org> Date: Mon, 19 May 2014 07:40:56 -0700 From: Randy Dunlap User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: Diego Viola , Rusty Russell CC: Andrew Morton , Linus Torvalds , Mateusz Guzik , Greg Kroah-Hartman , Steven Rostedt , LKML , Thomas Gleixner , "H. Peter Anvin" , Borislav Petkov , Ingo Molnar , Mel Gorman , Kay Sievers Subject: Re: [RFC PATCH] cmdline: Hide "debug" from /proc/cmdline References: <20140402144219.4cafbe37@gandalf.local.home> <20140402221212.GD16570@mguzik.redhat.com> <87wqf1oi22.fsf@rustcorp.com.au> <20140502153409.329d3b5b426275e8197251a2@linux-foundation.org> <871tw9c6kt.fsf@rustcorp.com.au> <53678ED6.4070502@infradead.org> <87eh07bu60.fsf@rustcorp.com.au> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/19/2014 01:11 AM, Diego Viola wrote: > I mean "e.g.:" is wrong, it should be e.g. or e.g., I don't see that in the wikipedia page. Are you basing that on "in this usage it is sometimes followed by a comma, depending on style."? I don't see a problem with the colon, since the quoted phrase has some conditions in it, like "sometimes" and "depending". Colons are often used to delimit a list or an example, but I'll leave it up to Rusty. > Sorry to be too nitpicky or annoying about this. > > Diego > > On Mon, May 19, 2014 at 5:06 AM, Diego Viola 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 wrote: >>> Randy Dunlap 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 >>> -- -- ~Randy