public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Markus Osterhoff <mo@mo-online.org>
Cc: linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
	Jiri Kosina <trivial@kernel.org>
Subject: Re: [TYPO 0/9] Several spellings and punctuations in Documentation
Date: Mon, 18 Aug 2014 00:25:21 -0700	[thread overview]
Message-ID: <53F1AA61.3080808@infradead.org> (raw)
In-Reply-To: <20140817182956.GA4077@mo-online.de>

On 08/17/14 11:29, Markus Osterhoff wrote:
> While reading some documentation to get acquainted with the Linux kernel
> development, I encountered some spelling and punctuation, erm, mutants
> that are addressed in this patch-set.
> 
> Patches are based on v3.17-rc1.
> 
> Since this is my first patch, any comments on style and email are
> welcome.

Hi Markus,

It would be nice (but not strictly required) for patches 1-9 to be
replies to (or references to) patch 0.
git-send-email can do this; see --thread.

> Markus Osterhoff (9):
>   [typo] spelling, punctuation in main README file
>   [typo] MAINTAINERS: redundant full stop removed
>   [typo] REPORTING-BUGS
>   [typo] COPYING: form feeds removed
>   [typo] CREDITS: capitalisation, punctuation
>   [typo] Doc/kbuild/kconfig-language.txt: several spellings
>   [typo] Doc/kbuild/kconfig-language.txt: sentence structure
>   [typo] Doc/CodingStyle, BUG-HUNTING, 00-INDEX
>   [typo] spelling, punctuation in Documentation/...

Patches should have a Subject: like
[PATCH 1/9] README: fix spelling and punctuation in main README file

I would prefer for these to all go thru the trivial patch maintainer:
Jiri Kosina <trivial@kernel.org>

That would involve adding the word "trivial" somewhere in the Subject line,
like (e.g.)
[PATCH 1/9 trivial] README: fix spelling and punctuation in main README file
or
[PATCH 1/9] trivial: fix spelling and punctuation in main README file


I can ack patches 1-3 and 5-8:
Acked-by: Randy Dunlap <rdunlap@infradead.org>


Thanks.

> 
>  COPYING                                   | 10 +++++-----
>  CREDITS                                   |  4 ++--
>  Documentation/00-INDEX                    |  4 ++--
>  Documentation/BUG-HUNTING                 | 10 +++++-----
>  Documentation/CodingStyle                 |  8 ++++----
>  Documentation/HOWTO                       | 22 +++++++++++-----------
>  Documentation/ManagementStyle             | 16 ++++++++--------
>  Documentation/SecurityBugs                |  2 +-
>  Documentation/SubmittingPatches           |  4 ++--
>  Documentation/kbuild/kconfig-language.txt | 18 +++++++++---------
>  MAINTAINERS                               |  2 +-
>  README                                    |  4 ++--
>  REPORTING-BUGS                            |  4 ++--
>  13 files changed, 54 insertions(+), 54 deletions(-)
> 


-- 
~Randy

      reply	other threads:[~2014-08-18  7:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-17 18:29 [TYPO 0/9] Several spellings and punctuations in Documentation Markus Osterhoff
2014-08-18  7:25 ` Randy Dunlap [this message]

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=53F1AA61.3080808@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mo@mo-online.org \
    --cc=trivial@kernel.org \
    /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