From: Peter Korsgaard <jacmet@sunsite.dk>
To: barebox@lists.infradead.org
Subject: [PATCH] documentation: It's U-Boot that doesn't have getopt, not Barebox
Date: Fri, 15 Jan 2010 11:39:33 +0100 [thread overview]
Message-ID: <1263551973-14588-1-git-send-email-jacmet@sunsite.dk> (raw)
Commit a3ffa97f (rename U-Boot-v2 project to barebox) also changed the
U-Boot references to Barebox in the getopt description, which doesn't
make much sense.
Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
---
Documentation/barebox-main.dox | 2 +-
README | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/barebox-main.dox b/Documentation/barebox-main.dox
index 42d1256..743add8 100644
--- a/Documentation/barebox-main.dox
+++ b/Documentation/barebox-main.dox
@@ -64,7 +64,7 @@ things right - without caring about losing support for old boards.
- getopt
- There is a small getopt implementation. Some commands got really
- complicated (both in code and in usage) due to the fact that @a barebox only
+ complicated (both in code and in usage) due to the fact that @a U-Boot only
allowed positional parameters.
- editor
diff --git a/README b/README
index 6f5fb26..9b5317d 100644
--- a/README
+++ b/README
@@ -61,7 +61,7 @@ Features
- getopt
There is a small getopt implementation. Some commands got really
- complicated (both in code and in usage) due to the fact that barebox only
+ complicated (both in code and in usage) due to the fact that U-Boot only
allowed positional parameters.
- editor
--
1.6.5
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2010-01-15 10:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 10:39 Peter Korsgaard [this message]
2010-01-16 11:31 ` Sascha Hauer
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=1263551973-14588-1-git-send-email-jacmet@sunsite.dk \
--to=jacmet@sunsite.dk \
--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