From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 8f1fe7c5314aae2893a52959f0d06dd9c0d28d00
Date: Sun, 27 Sep 2015 10:57:40 +0200 [thread overview]
Message-ID: <20150927085740.9E7BE20FF1@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1744 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 8f1fe7c5314aae2893a52959f0d06dd9c0d28d00 (commit)
from ccb8e47d0eafccef6b69c7094b3330dc95eeef54 (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 8f1fe7c5314aae2893a52959f0d06dd9c0d28d00
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Sep 27 10:56:34 2015 +0200
core94: fix chrontab modification check for dma.
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/94/update.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/94/update.sh b/config/rootfiles/core/94/update.sh
index 7dca2a1..ff9797c 100644
--- a/config/rootfiles/core/94/update.sh
+++ b/config/rootfiles/core/94/update.sh
@@ -56,7 +56,7 @@ mv -f /etc/ssh/ssh_host_rsa_key{,.old}
sed -i /var/spool/cron/root.orig -e "/Force an update once a month/d"
sed -i /var/spool/cron/root.orig -e "/ddns update-all --force/d"
-grep -qv "dma -q" || cat <<EOF >> /var/spool/cron/root.orig
+grep -q "dma -q" /var/spool/cron/root.orig || cat <<EOF >> /var/spool/cron/root.orig
# Retry sending spooled mails regularly
%hourly * /usr/sbin/dma -q
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-09-27 8:57 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=20150927085740.9E7BE20FF1@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