From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, thirteen, updated. 6da6905a95d224f80fe65a19ae00ab911381e04a
Date: Fri, 21 Dec 2012 09:45:57 +0100 [thread overview]
Message-ID: <20121221084558.33CCD20045@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1760 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, thirteen has been updated
via 6da6905a95d224f80fe65a19ae00ab911381e04a (commit)
from e54330e01e20314f796543d2d2e5eb34ee43caf3 (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 6da6905a95d224f80fe65a19ae00ab911381e04a
Author: Arne Fitzenreiter <Arne_F(a)ipfire.org>
Date: Thu Dec 20 23:33:11 2012 +0100
IPFire 2.13beta1.
-----------------------------------------------------------------------
Summary of changes:
make.sh | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/make.sh b/make.sh
index 0934909..21808c9 100755
--- a/make.sh
+++ b/make.sh
@@ -24,7 +24,7 @@
NAME="IPFire" # Software name
SNAME="ipfire" # Short name
-VERSION="2.13" # Version number
+VERSION="2.13beta1" # Version number
CORE="65" # Core Level (Filename)
PAKFIRE_CORE="65" # Core Level (PAKFIRE)
GIT_BRANCH=`git status | head -n1 | cut -d" " -f4` # Git Branch
@@ -760,7 +760,7 @@ buildipfire() {
cat /proc/cpuinfo >> $BASEDIR/build/var/ipfire/firebuild
echo $PAKFIRE_CORE > $BASEDIR/build/opt/pakfire/db/core/mine
case "$GIT_BRANCH" in
- core*)
+ core*|beta?|rc?)
echo "$NAME $VERSION ($MACHINE) - $GIT_BRANCH" > $BASEDIR/build/etc/system-release
;;
*)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2012-12-21 8:45 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=20121221084558.33CCD20045@argus.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