From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 66028310ce91a19618376223ca0f44e7adbdfaf7
Date: Thu, 23 Nov 2017 16:10:26 +0000 [thread overview]
Message-ID: <20171123161027.12B791081BCF@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2671 bytes --]
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "IPFire 2.x development tree".
The branch, next has been updated
via 66028310ce91a19618376223ca0f44e7adbdfaf7 (commit)
via f3b7cf47caba72ed24d02b014f11cb14c7ea33a2 (commit)
via 543286056ee211d4018b93cb866a63d2686a16dc (commit)
from f978327791ec8fd4cba6b92c2288434ed43841ab (commit)
Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.
- Log -----------------------------------------------------------------
commit 66028310ce91a19618376223ca0f44e7adbdfaf7
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Nov 23 16:09:00 2017 +0000
make.sh: Don't try to dump a non-existing logfile
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
commit f3b7cf47caba72ed24d02b014f11cb14c7ea33a2
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Nov 23 16:07:42 2017 +0000
make.sh: Show architecture we are building the toolchain for
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
commit 543286056ee211d4018b93cb866a63d2686a16dc
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Nov 23 16:06:59 2017 +0000
make.sh: Fix typo
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
make.sh | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
Difference in files:
diff --git a/make.sh b/make.sh
index c088057..44516af 100755
--- a/make.sh
+++ b/make.sh
@@ -369,7 +369,7 @@ exiterror() {
done
# Dump logfile
- if [ -n "${LOGFILE}" ]; then
+ if [ -n "${LOGFILE}" ] && [ -e "${LOGFILE}" ]; then
echo # empty line
local line
@@ -391,7 +391,7 @@ exiterror() {
prepareenv() {
# Are we running the right shell?
- if [ ! -z "${BASH}" ]; then
+ if [ -z "${BASH}" ]; then
exiterror "BASH environment variable is not set. You're probably running the wrong shell."
fi
@@ -1778,7 +1778,7 @@ toolchain)
${INTERACTIVE} && clear
prepareenv
- print_build_stage "Toolchain compilation"
+ print_build_stage "Toolchain compilation (${BUILD_ARCH})"
buildtoolchain
echo "`date -u '+%b %e %T'`: Create toolchain image for ${BUILD_ARCH}" | tee -a $LOGFILE
test -d $BASEDIR/cache/toolchains || mkdir -p $BASEDIR/cache/toolchains
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-11-23 16:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20171123161027.12B791081BCF@git01.ipfire.org \
--to=git@ipfire.org \
--cc=ipfire-scm@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