Linux Hotplug development
 help / color / mirror / Atom feed
From: Michael Witten <mfwitten@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PULL] Docs: udev.xml: Copyediting
Date: Fri, 15 Apr 2011 17:41:50 +0000	[thread overview]
Message-ID: <ad0ad506-864e-4c49-8b3e-95fbaf8d55df-mfwitten@gmail.com> (raw)
In-Reply-To: <5cb4f3ce-b6e7-4c2a-b175-2081daad3acb-mfwitten@gmail.com>

On Mon, 11 Apr 2011 06:31:30 +0000, Michael Witten wrote:

> I did some copyediting whilst looking through udev/udev.xml;
> 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/udev.xml
>
> Squash them if desired.
>
>       Docs: udev.xml: Offset daemon name with commas
>       Docs: udev.xml: Remove commas (and unnecessary repetition)
>       Docs: udev.xml: `are' -> `is'; the subject is `Access'
>       Docs: udev.xml: Use present tense
>       Docs: udev.xml: Clarification through proper wording
>       Docs: udev.xml: `,' -> `;'
>       Docs: udev.xml: `key value' -> `key-value'
>       Docs: udev.xml: `,' -> `:'
>       Docs: udev.xml: Use `assignment' consistently
>       Docs: udev.xml: `comma-separated' is a better description
>       Docs: udev.xml: Remove unnecessary repitition
>       Docs: udev.xml: Add a few more words for context
>       Docs: udev.xml: Use `unless' for clarity
>       Docs: udev.xml: Clarify PROGRAM key
>       Docs: udev.xml: `a shell style' -> `shell-style'
>       Docs: udev.xml: Clean `*' description
>       Docs: udev.xml: Clean character range description
>       Docs: udev.xml: Clean up description of NAME assignment key
>       Docs: udev.xml: Clean up description of SYMLINK assignment key
>       Docs: udev.xml: Clean up description of ENV assignment key
>       Docs: udev.xml: Clean up description of RUN assignment key
>       Docs: udev.xml: Clean up description of LABEL assignment key
>       Docs: udev.xml: Add missing `.'
>       Docs: udev.xml: `which' -> `content of which'
>       Docs: udev.xml: `commandline' -> `command line'
>       Docs: udev.xml: Clean up WAIT_FOR description
>       Docs: udev.xml: `a' -> `the'
>       Docs: udev.xml: Clean up introduction to substitutions.
>       Docs: udev.xml: Use normal sentence structure
>       Docs: udev.xml: Actually make a separate paragraph
>       Docs: udev.xml: Add comma
>       Docs: udev.xml: `char' -> `character'
>       Docs: udev.xml: `comma-separated' is a better description
>       Docs: udev.xml: Clarify through a change in word ordering
>       Docs: udev.xml: Improved word order
>       Docs: udev.xml: Fix dangling modifier
>
>  udev/udev.xml |  169 +++++++++++++++++++++++++++++----------------------------
>  1 files changed, 86 insertions(+), 83 deletions(-)
>
> [diff]

Would someone like to commit this?

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-11  6:31 [PULL] Docs: udev.xml: Copyediting Michael Witten
2011-04-15 17:41 ` Michael Witten [this message]
2011-05-16  2:29 ` Michael Witten
2011-05-17 23:07 ` 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=ad0ad506-864e-4c49-8b3e-95fbaf8d55df-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