lkml.org 
[lkml]   [2014]   [Jan]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRe: [PATCH] include/linux/regmap.h: fix a couple of typos
From
On Thu, Jan 9, 2014 at 2:43 AM, Randy Dunlap <rdunlap@infradead.org> wrote:
> On 01/08/14 17:46, Laszlo Papp wrote:
>> On Wed, Jan 8, 2014 at 9:49 PM, Mark Brown <broonie@kernel.org> wrote:
>>> On Wed, Jan 08, 2014 at 09:08:44PM +0000, Laszlo Papp wrote:
>>>> On Wed, Jan 8, 2014 at 9:02 PM, Laszlo Papp <lpapp@kde.org> wrote:
>>>
>>>>> That being said, I will not have time, nor the motivation to argue
>>>>> over such a nuance, so feel free to reject the change.
>>>
>>>> Of course, this is just on top of the vim spell checker error as I
>>>> wrote in the commit message...
>>>
>>>> Oh yes, and one more factual data in here:
>>>
>>>> lpapp ~/Projects/linux-staging $ grep -rn "e\.g\." . | wc -l
>>>> 3447
>>>
>>>> lpapp ~/Projects/linux-staging $ grep -rn " eg," | wc -l
>>>> 18
>>>
>>> That's not the issue - it's dropping the comma. It's either "e.g." or
>>> "eg", the comma is a separate thing providing a break between clauses.
>>> Strictly it should have the periods since it is an abbreviation but
>>> their use is more vauge in fixed point text since they look ugly, the
>>> thing that made me complain was that you dropped the comma as well as
>>> substituting in the expanded version.
>>
>> I still do not get what point you are trying to make. Could you please
>> provide evidence? Because really, this is the usage I have seen in
>> projects out there all around, including the majority of the linux
>> kernel.
>>
>> Here is some more data:
>>
>> grep -rn "e\.g\. " . | wc -l
>> 2553
>> lpapp ~/Projects/linux-staging $ grep -rn "e\.g\.," . | wc -l
>> 573
>> --
>
> Hi,
>
> I am used to seeing e.g. and i.e. always followed by a comma when they are
> used to begin a sentence. However, I just checked and some online style
> guides say to omit the comma and some say to use it, and we (Linux kernel)
> don't really have a writing style guide to look at. I think that makes it
> up to the maintainer to decide what is acceptable.

Who is the maintainer? Is it Mark, or I should wait for someone else?


\
 
 \ /
  Last update: 2014-01-09 12:01    [W:0.167 / U:0.628 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site