Linux Hotplug development
 help / color / mirror / Atom feed
From: Michael Witten <mfwitten@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PULL] Docs: README: Copyediting
Date: Fri, 15 Apr 2011 17:40:53 +0000	[thread overview]
Message-ID: <5894efb2-c7f1-4359-bb5a-3bdee4370b89-mfwitten@gmail.com> (raw)
In-Reply-To: <6169a635-4560-4e13-822f-a815cc6e7a4c-mfwitten@gmail.com>

On Mon, 11 Apr 2011 06:22:57 +0000, Michael Witten wrote:

> I did some copyediting whilst looking through the README;
> this email contains a pull request as well as the inlined
> diff of all the changes squashed together.
>
> The changes apply cleanly to 960250952193db522b8ced336bf998bd7e8e4a31:
>
>   selinux: firmware - do not label files in runtime dir (2011-04-08 03:08:16 +0200)
>
> and are available here:
>
>   git://github.com/mfwitten/udev.git docs/README
>
> Squash them if desired.
>
>       Docs: README: `to replace' -> `replacing'
>       Docs: README: `,' -> `;'
>       Docs: README: Clean up a sentence
>       Docs: README: Use present tense
>       Docs: README: Add missing `and'
>       Docs: README: Remove commas and use subjective mood
>       Docs: README: Clean up `udev extras' requirements
>       Docs: README: Clarify configuration of existing devices
>       Docs: README: `does never apply' -> `never applies'
>       Docs: README: Flip sentence structure to improve wording
>       Docs: README: `set up' is the verb; `setup' is a noun
>       Docs: README: Add a comma to offset the modifier
>
>  README |   44 ++++++++++++++++++++++----------------------
>  1 files changed, 22 insertions(+), 22 deletions(-)
>
> [diff]

Would someone like to commit this?

  reply	other threads:[~2011-04-15 17:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11  6:22 [PULL] Docs: README: Copyediting Michael Witten
2011-04-15 17:40 ` Michael Witten [this message]
2011-04-18  3:11 ` Kay Sievers

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=5894efb2-c7f1-4359-bb5a-3bdee4370b89-mfwitten@gmail.com \
    --to=mfwitten@gmail.com \
    --cc=linux-hotplug@vger.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