From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, core64, updated. 145f3588120ca2a576af262358bb9266ceff6327
Date: Sun, 11 Nov 2012 11:15:09 +0100 [thread overview]
Message-ID: <20121111101509.C5C72200C3@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1573 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, core64 has been updated
via 145f3588120ca2a576af262358bb9266ceff6327 (commit)
from 6f8891ccc776e62448e1e08d3efbada21a8fd447 (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 145f3588120ca2a576af262358bb9266ceff6327
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Nov 11 11:14:22 2012 +0100
core64: add need reboot if outgoingfw is used.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/64/update.sh | 6 ++++--
1 files changed, 4 insertions(+), 2 deletions(-)
Difference in files:
diff --git a/config/rootfiles/core/64/update.sh b/config/rootfiles/core/64/update.sh
index c1e7545..54339ef 100644
--- a/config/rootfiles/core/64/update.sh
+++ b/config/rootfiles/core/64/update.sh
@@ -71,8 +71,10 @@ perl -e "require '/var/ipfire/lang.pl'; &Lang::BuildCacheLang"
sync
-# This update need a reboot...
-#touch /var/run/need_reboot
+# This update need a reboot if outgoingfw is used
+if [ -s /var/ipfire/outgoing/rules ]; then
+ touch /var/run/need_reboot
+fi
#
#Finish
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2012-11-11 10:15 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=20121111101509.C5C72200C3@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