mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Pavel Machek <pavel@ucw.cz>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] Cleanups to Doc*/SubmittingPatches
Date: Sun, 14 May 2006 10:12:54 -0700	[thread overview]
Message-ID: <20060514101254.f731daf1.rdunlap@xenotime.net> (raw)
In-Reply-To: <20060514143037.GA2886@elf.ucw.cz>

On Sun, 14 May 2006 16:30:38 +0200 Pavel Machek wrote:

> This cleans up Submitting patches a bit. Missing/inconsistent full
> stops, mostly.

Incomplete sentences (fragments) don't need full stops, but they
should be consistent.

> diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
> index c2c85bc..07b87ce 100644
> --- a/Documentation/SubmittingPatches
> +++ b/Documentation/SubmittingPatches
> @@ -173,17 +173,17 @@ copy the maintainer when you change thei
>  For small patches you may want to CC the Trivial Patch Monkey
>  trivial@kernel.org managed by Adrian Bunk; which collects "trivial"
>  patches. Trivial patches must qualify for one of the following rules:
> - Spelling fixes in documentation
> + Spelling fixes in documentation.
>   Spelling fixes which could break grep(1).

I would just remove that '.' above and skip the rest of the
changes in this section.

> - Warning fixes (cluttering with useless warnings is bad)
> - Compilation fixes (only if they are actually correct)
> - Runtime fixes (only if they actually fix things)
> + Warning fixes (cluttering with useless warnings is bad).
> + Compilation fixes (only if they are actually correct).
> + Runtime fixes (only if they actually fix things).
>   Removing use of deprecated functions/macros (eg. check_region).
> - Contact detail and documentation fixes
> + Contact detail and documentation fixes.
>   Non-portable code replaced by portable code (even in arch-specific,
> - since people copy, as long as it's trivial)
> - Any fix by the author/maintainer of the file. (ie. patch monkey
> - in re-transmission mode)
> + since people copy, as long as it's trivial).
> + Any fix by the author/maintainer of the file (ie. patch monkey
> + in re-transmission mode).
>  URL: <http://www.kernel.org/pub/linux/kernel/people/bunk/trivial/>

---
~Randy

  reply	other threads:[~2006-05-14 17:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-14 14:30 Pavel Machek
2006-05-14 17:12 ` Randy.Dunlap [this message]
2006-05-14 17:23   ` Pavel Machek
2006-05-14 17:59     ` Randy.Dunlap
2006-05-15  8:42       ` Steven Rostedt

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=20060514101254.f731daf1.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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

all inboxes | Powered by JetHome®