From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [IPFire-SCM] [git.ipfire.org] IPFire 2.x development tree branch, master, updated. cd025baaceeabdd1fd50af0476dfedacb8f60ce6
Date: Sun, 22 Jul 2012 10:25:44 +0200 [thread overview]
Message-ID: <20120722082545.2FB12200B9@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1646 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 cd025baaceeabdd1fd50af0476dfedacb8f60ce6 (commit)
from 6665a03d7c6492f07d989c7c5bccc488a5c7a9cf (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 cd025baaceeabdd1fd50af0476dfedacb8f60ce6
Author: Arne Fitzenreiter <arne.fitzenreiter(a)ipfire.org>
Date: Sun Jul 22 10:25:10 2012 +0200
close core61.
-----------------------------------------------------------------------
Summary of changes:
make.sh | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
mode change 100755 => 100644 html/cgi-bin/proxy.cgi
Difference in files:
diff --git a/html/cgi-bin/proxy.cgi b/html/cgi-bin/proxy.cgi
old mode 100755
new mode 100644
diff --git a/make.sh b/make.sh
index 89f979d..265677b 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="61" # Core Level (Filename)
-PAKFIRE_CORE="60" # Core Level (PAKFIRE)
+PAKFIRE_CORE="61" # 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-07-22 8:25 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=20120722082545.2FB12200B9@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