From: Sascha Hauer <s.hauer@pengutronix.de>
To: Alan Ott <alan@signal11.us>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH] README: change path to sandbox environment
Date: Mon, 21 May 2012 22:06:26 +0200 [thread overview]
Message-ID: <20120521200626.GH30400@pengutronix.de> (raw)
In-Reply-To: <1337615641-7246-1-git-send-email-alan@signal11.us>
On Mon, May 21, 2012 at 11:54:01AM -0400, Alan Ott wrote:
> The path to the sandbox environment is now arch/sandbox/board/env .
>
> Signed-off-by: Alan Ott <alan@signal11.us>
Also applied
Sascha
> ---
> README | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/README b/README
> index c875b7d..cec9ccb 100644
> --- a/README
> +++ b/README
> @@ -110,7 +110,7 @@ Barebox usually needs an environment for storing the configuration data.
> You can generate an environment using the example environment contained
> in board/sandbox/env:
>
> - # ./scripts/bareboxenv -s -p 0x10000 board/sandbox/env/ env.bin
> + # ./scripts/bareboxenv -s -p 0x10000 arch/sandbox/board/env env.bin
>
> To get some files to play with you can generate a cramfs image:
> # mkcramfs somedir/ cramfs.bin
> --
> 1.7.0.4
>
>
> _______________________________________________
> 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
prev parent reply other threads:[~2012-05-21 20:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-21 15:54 Alan Ott
2012-05-21 20:06 ` 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=20120521200626.GH30400@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=alan@signal11.us \
--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