From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] make.sh: Clarify options need to come before the actual command
Date: Sun, 09 Jan 2022 13:54:05 +0100 [thread overview]
Message-ID: <31f0870d-f1c9-9f29-48d6-eaa9040aab7e@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
This might prevent some misunderstandings, as the help of make.sh does
not precisely state where the options (target architecture) needs to be
specified.
See: https://lists.ipfire.org/pipermail/development/2022-January/011911.html
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
make.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/make.sh b/make.sh
index 7568ee232..3f45e1953 100755
--- a/make.sh
+++ b/make.sh
@@ -1957,7 +1957,7 @@ check-manualpages)
fi
;;
*)
- echo "Usage: $0 {build|changelog|clean|gettoolchain|downloadsrc|shell|sync|toolchain|update-contributors|find-dependencies|check-manualpages}"
+ echo "Usage: $0 [OPTIONS] {build|changelog|clean|gettoolchain|downloadsrc|shell|sync|toolchain|update-contributors|find-dependencies|check-manualpages}"
cat doc/make.sh-usage
;;
esac
--
2.26.2
next reply other threads:[~2022-01-09 12:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 12:54 Peter Müller [this message]
2022-01-09 15:20 ` Michael Tremer
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=31f0870d-f1c9-9f29-48d6-eaa9040aab7e@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.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