From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 4ea955c544fa5ff4939449bc163426fc36e1482f
Date: Mon, 02 Dec 2013 21:41:25 +0100 [thread overview]
Message-ID: <20131202204126.39AF42155D@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1626 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 4ea955c544fa5ff4939449bc163426fc36e1482f (commit)
from 9f9e43dcdd2517cdd56810a243270e3697844569 (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 4ea955c544fa5ff4939449bc163426fc36e1482f
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Dec 2 21:41:12 2013 +0100
core74: Fix incrementation.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/74/update.sh | 1 +
1 file changed, 1 insertion(+)
Difference in files:
diff --git a/config/rootfiles/core/74/update.sh b/config/rootfiles/core/74/update.sh
index 3f8abce..ca26b51 100644
--- a/config/rootfiles/core/74/update.sh
+++ b/config/rootfiles/core/74/update.sh
@@ -48,6 +48,7 @@ if [ -e "/var/ipfire/proxy/enable" ] || [ -e "/var/ipfire/proxy/enable_blue" ];
eval $(/usr/local/bin/readhash /var/ipfire/proxy/advanced/settings)
if [ "${TRANSPARENT_PORT}" = "81" ]; then
+ TRANSPARENT_PORT="$(( ${TRANSPARENT_PORT} + 1 ))"
sed -e "s/^TRANSPARENT_PORT=.*/TRANSPARENT_PORT=${TRANSPARENT_PORT}/" \
-i /var/ipfire/proxy/advanced/settings
fi
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-12-02 20:41 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=20131202204126.39AF42155D@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