Re: [TYPO 9/9] [typo] spelling, punctuation in Documentation/...

[Markus Osterhoff <mo@mo-online.org>]

Dear Randy,

thanks for you reply.

* Randy Dunlap <rdunlap@infradead.org> [140818 09:37]:
> On 08/17/14 11:30, Markus Osterhoff wrote:
> > diff --git a/Documentation/HOWTO b/Documentation/HOWTO
> > -gcc`) for some information on them.
> > +gcc') for some information on them.
> Backquotes imply that the contents (string) can be entered at a shell prompt;
> i.e., they are a command.
Ah, I see.

> > -It is worth mentioning what Andrew Morton wrote on the linux-kernel
> > +It is worth mentioning what Andrew Morton wrote on the Linux-kernel
> The mailing list is "linux-kernel".
Stupid me, sorry :)

> > diff --git a/Documentation/ManagementStyle b/Documentation/ManagementStyle
> > -Btw, when talking about "kernel manager", it's all about the technical
> > +Btw., when talking about "kernel manager", it's all about the technical
> BTW (or Btw) is common -- no period.
Okay.

> > diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> > index 0a523c9..a358031 100644
> > --- a/Documentation/SubmittingPatches
> > +++ b/Documentation/SubmittingPatches
> > @@ -227,8 +227,8 @@ Linux kernel.  His e-mail address is <torvalds@linux-foundation.org>.
> >  He gets a lot of e-mail, so typically you should do your best to -avoid-
> >  sending him e-mail. 
> >  
> > -Patches which are bug fixes, are "obvious" changes, or similarly
> > -require little discussion should be sent or CC'd to Linus.  Patches
> > +Patches, which are bug fixes, are "obvious" changes, or similarly
> 
>    Patches which are bug fixes or "obvious" changes or similarly
> 
> > +require little discussion, should be sent or CC'd to Linus.  Patches
>   why the added comma?
My feeling is this increases the comprehensibility.

> >  which require discussion or do not have a clear advantage should
> >  usually be sent first to linux-kernel.  Only after the patch is
> >  discussed should the patch then be submitted to Linus.
Greetings,
Markus