public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 5b6fdbf9d5cf00bcba7d78bfaa8dd976a5d96411
Date: Sat, 12 May 2012 19:22:52 +0200	[thread overview]
Message-ID: <20120512172252.6915820144@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1490 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  5b6fdbf9d5cf00bcba7d78bfaa8dd976a5d96411 (commit)
      from  7f76d8cb4aa2a932fd1b00f0f55110a7ea4d3ee1 (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 5b6fdbf9d5cf00bcba7d78bfaa8dd976a5d96411
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sat May 12 19:22:26 2012 +0200

    finished core59.

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

Summary of changes:
 make.sh |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

Difference in files:
diff --git a/make.sh b/make.sh
index 4e79793..9b27f05 100755
--- a/make.sh
+++ b/make.sh
@@ -26,7 +26,7 @@ NAME="IPFire"							# Software name
 SNAME="ipfire"							# Short name
 VERSION="2.11"							# Version number
 CORE="59"							# Core Level (Filename)
-PAKFIRE_CORE="58"						# Core Level (PAKFIRE)
+PAKFIRE_CORE="59"						# 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:[~2012-05-12 17:22 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=20120512172252.6915820144@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