public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 0e1fcef0180f7b6542be989f2c53db27c3cdd522
Date: Fri, 20 Mar 2015 11:21:26 +0100	[thread overview]
Message-ID: <20150320102126.CC61422065@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1544 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  0e1fcef0180f7b6542be989f2c53db27c3cdd522 (commit)
      from  5f7a8b7e1cf7d665fc4df8757bf54d5d08903a88 (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 0e1fcef0180f7b6542be989f2c53db27c3cdd522
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Fri Mar 20 11:20:45 2015 +0100

    set version to IPFire-2.17 core89

-----------------------------------------------------------------------

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 d049888..4deb3c8 100755
--- a/make.sh
+++ b/make.sh
@@ -25,8 +25,8 @@
 NAME="IPFire"							# Software name
 SNAME="ipfire"							# Short name
 VERSION="2.17"							# Version number
-CORE="88"							# Core Level (Filename)
-PAKFIRE_CORE="88"						# Core Level (PAKFIRE)
+CORE="89"							# Core Level (Filename)
+PAKFIRE_CORE="89"						# Core Level (PAKFIRE)
 GIT_BRANCH=`git rev-parse --abbrev-ref HEAD`			# 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:[~2015-03-20 10:21 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=20150320102126.CC61422065@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