Poky Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Scott Rifenbark <scott.m.rifenbark@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 1/1] documentation/yocto-project-qs/yocto-project-qs.xml: Fixed grammar problem
Date: Mon, 20 Dec 2010 14:44:12 +0000	[thread overview]
Message-ID: <1292856252.25087.4468.camel@rex> (raw)
In-Reply-To: <df55c574e165951fcd95df1471a658576681be81.1292534378.git.scott.m.rifenbark@intel.com>

On Wed, 2010-12-15 at 15:05 -0800, Scott Rifenbark wrote:
> Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
> ---
>  .../yocto-project-qs/yocto-project-qs.xml          |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml
> index 6575469..1c45cde 100644
> --- a/documentation/yocto-project-qs/yocto-project-qs.xml
> +++ b/documentation/yocto-project-qs/yocto-project-qs.xml
> @@ -269,7 +269,7 @@
>       $ poky-qemu qemux86
>               </literallayout>
>               The build process could take several hours the first time you run it. 
> -             Depending on the number of processor and cores, the amount or RAM, the speed of your
> +             Depending on the number of processors and cores, the amount or RAM, the speed of your
>               internet connection and other factors.
>               After the initial build, subsequent builds run much faster.
>           </para>

Merged into master, thanks.

Richard



  reply	other threads:[~2010-12-20 14:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-16 21:19 [PATCH 0/1] Docs: Updating Yocto Quick Start Scott Rifenbark
2010-12-15 23:05 ` [PATCH 1/1] documentation/yocto-project-qs/yocto-project-qs.xml: Fixed grammar problem Scott Rifenbark
2010-12-20 14:44   ` Richard Purdie [this message]
2010-12-20 15:48 ` [PATCH 0/1] Docs: Updating Yocto Quick Start Richard Purdie

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=1292856252.25087.4468.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=poky@yoctoproject.org \
    --cc=scott.m.rifenbark@intel.com \
    /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