mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Antony Pavlov <antonynpavlov@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] README: fix some typos
Date: Mon, 7 May 2012 09:55:52 +0200	[thread overview]
Message-ID: <20120507075552.GD4141@pengutronix.de> (raw)
In-Reply-To: <1336258510-22036-1-git-send-email-antonynpavlov@gmail.com>

On Sun, May 06, 2012 at 02:55:10AM +0400, Antony Pavlov wrote:
> Signed-off-by: Antony Pavlov <antonynpavlov@gmail.com>
> ---
>  README |    6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

Applied, thanks.

Sascha

> 
> diff --git a/README b/README
> index 5662a1c..c875b7d 100644
> --- a/README
> +++ b/README
> @@ -56,7 +56,7 @@ Features
>    'eth0.ip=192.168.0.7' or 'echo $eth0.ip'
>  
>  - initcalls
> -  hooks in the startup process can be archieved with *_initcall() directives
> +  hooks in the startup process can be achieved with *_initcall() directives
>    in each file.
>  
>  - getopt
> @@ -95,7 +95,7 @@ This command starts a menu box and lets you select all the different
>  options available for your architecture. Once the configuration was
>  finished (you can simulate this by using the standard demo config file
>  with 'make sandbox_defconfig'), there is a .config file in the toplevel
> -directory of the sourcode.
> +directory of the source code.
>  
>  Once barebox is configured, we can start the compilation
>  
> @@ -106,7 +106,7 @@ If everything goes well, the result is a file called barebox:
>    # ls -l barebox
>      -rwxr-xr-x 1 rsc ptx 114073 Jun 26 22:34 barebox
>  
> -Barebox usually needs an environment for storing the configuation data.
> +Barebox usually needs an environment for storing the configuration data.
>  You can generate an environment using the example environment contained
>  in board/sandbox/env:
>  
> -- 
> 1.7.10
> 
> 
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2012-05-07  7:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-05 22:55 Antony Pavlov
2012-05-07  7:55 ` Sascha Hauer [this message]

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=20120507075552.GD4141@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=antonynpavlov@gmail.com \
    --cc=barebox@lists.infradead.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