From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 9c7d04fe5ef7e75ccde5e0446ed1d1c1ca02c537
Date: Sat, 19 Jan 2013 12:49:55 +0100 [thread overview]
Message-ID: <20130119114955.55BD9200BF@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1388 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 9c7d04fe5ef7e75ccde5e0446ed1d1c1ca02c537 (commit)
from 963f4bffca99d8b19a3149ae280a4308c0fc9e70 (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 9c7d04fe5ef7e75ccde5e0446ed1d1c1ca02c537
Author: Arne Fitzenreiter <Arne_F(a)ipfire.org>
Date: Sat Jan 19 12:48:49 2013 +0100
IPFire 2.13beta2.
-----------------------------------------------------------------------
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 95c80cb..29facbf 100755
--- a/make.sh
+++ b/make.sh
@@ -24,7 +24,7 @@
NAME="IPFire" # Software name
SNAME="ipfire" # Short name
-VERSION="2.13beta1" # Version number
+VERSION="2.13beta2" # Version number
CORE="65" # Core Level (Filename)
PAKFIRE_CORE="65" # Core Level (PAKFIRE)
GIT_BRANCH=`git status | head -n1 | cut -d" " -f4` # Git Branch
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-01-19 11:49 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=20130119114955.55BD9200BF@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