lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <53F1AA61.3080808@infradead.org>
Date:	Mon, 18 Aug 2014 00:25:21 -0700
From:	Randy Dunlap <rdunlap@...radead.org>
To:	Markus Osterhoff <mo@...online.org>
CC:	linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org,
	Jiri Kosina <trivial@...nel.org>
Subject: Re: [TYPO 0/9] Several spellings and punctuations in Documentation

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@...nel.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@...radead.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ