From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. deb99a74d30d4bcb69abf02265ce2dd4db65bf14
Date: Sat, 20 May 2017 10:19:06 +0100 [thread overview]
Message-ID: <20170520091906.A501310853C3@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1573 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 deb99a74d30d4bcb69abf02265ce2dd4db65bf14 (commit)
from 0ff77cf478fcbd098eba4df40eacf09711415f8c (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 deb99a74d30d4bcb69abf02265ce2dd4db65bf14
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sun Apr 30 12:12:41 2017 +0100
make.sh: Show architecture we are building for
Signed-off-by: Michael Tremer <michael.tremer(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
tools/make-functions | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/tools/make-functions b/tools/make-functions
index 356162f..62f1664 100644
--- a/tools/make-functions
+++ b/tools/make-functions
@@ -223,7 +223,7 @@ beautify()
LAST_STAGE_TIME=$[ `date +%s` - $STAGE_TIME_START ]
fi
STAGE_TIME_START=`date +%s`
- echo -ne "${BOLD}*** ${MESSAGE}${NORMAL}"
+ echo -ne "${BOLD}*** (${BUILD_ARCH}) ${MESSAGE}${NORMAL}"
if [ "$LAST_STAGE_TIME" ]; then
echo -ne "${DONE} (Last stage took $LAST_STAGE_TIME secs)${NORMAL}"
fi
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2017-05-20 9:19 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=20170520091906.A501310853C3@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