From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 9ff65bfac3f7de2bc1dc88e82b8315c4ef4c48cc
Date: Wed, 26 Feb 2020 18:19:13 +0000 [thread overview]
Message-ID: <48SPFs6D9Gz2y0G@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1612 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, master has been updated
via 9ff65bfac3f7de2bc1dc88e82b8315c4ef4c48cc (commit)
from 5ad31551cd8e22b9dcf19739e4369969514bdca8 (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 9ff65bfac3f7de2bc1dc88e82b8315c4ef4c48cc
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Feb 26 18:16:00 2020 +0000
make.sh: add core to version string
this make it easier to find the unstable and testing build for a core update in fireinfo.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
make.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/make.sh b/make.sh
index 2e396fd8e..07c0f52c2 100755
--- a/make.sh
+++ b/make.sh
@@ -515,7 +515,7 @@ prepareenv() {
system_release="${system_release} - ${GIT_BRANCH}"
;;
*)
- system_release="${system_release} - Development Build: ${GIT_BRANCH}/${GIT_LASTCOMMIT:0:8}"
+ system_release="${system_release} - core${CORE} Development Build: ${GIT_BRANCH}/${GIT_LASTCOMMIT:0:8}"
;;
esac
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-02-26 18: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=48SPFs6D9Gz2y0G@people01.haj.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