From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 3ab685b34bd439f77c2f90f4c8214b025eb99e1c
Date: Thu, 14 Feb 2013 22:19:18 +0100 [thread overview]
Message-ID: <20130214211918.69BAA200BB@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1580 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 3ab685b34bd439f77c2f90f4c8214b025eb99e1c (commit)
from 2de6c6499478531367c663b5d8f7410fe49af3aa (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 3ab685b34bd439f77c2f90f4c8214b025eb99e1c
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Feb 14 22:16:16 2013 +0100
IPFire 2.13 final.
-----------------------------------------------------------------------
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 8d42e47..05be857 100755
--- a/make.sh
+++ b/make.sh
@@ -24,9 +24,9 @@
NAME="IPFire" # Software name
SNAME="ipfire" # Short name
-VERSION="2.13rc2" # Version number
-CORE="65" # Core Level (Filename)
-PAKFIRE_CORE="65" # Core Level (PAKFIRE)
+VERSION="2.13" # Version number
+CORE="66" # Core Level (Filename)
+PAKFIRE_CORE="66" # Core Level (PAKFIRE)
GIT_BRANCH=`git status | head -n1 | cut -d" " -f4` # Git Branch
SLOGAN="www.ipfire.org" # Software slogan
CONFIG_ROOT=/var/ipfire # Configuration rootdir
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-02-14 21: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=20130214211918.69BAA200BB@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