From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 261624fb991083f07246e2d3d7a24b2d1ff18c35
Date: Thu, 17 Jul 2014 07:00:32 +0200 [thread overview]
Message-ID: <20140717050032.8113E21001@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1576 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 261624fb991083f07246e2d3d7a24b2d1ff18c35 (commit)
from 3a99677dd6d6251dbe1cc8b70f7e55957230ac29 (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 261624fb991083f07246e2d3d7a24b2d1ff18c35
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Jul 17 06:59:37 2014 +0200
checkwronglinks: add a check for var/run/* in rootfiles.
-----------------------------------------------------------------------
Summary of changes:
tools/checkwronginitlinks | 7 +++++++
1 file changed, 7 insertions(+)
Difference in files:
diff --git a/tools/checkwronginitlinks b/tools/checkwronginitlinks
index 6f001c0..65fc946 100755
--- a/tools/checkwronginitlinks
+++ b/tools/checkwronginitlinks
@@ -25,3 +25,10 @@ if [ "${?}" == "0" ]; then
grep -r "^etc/init.d//*" ./config/rootfiles/
echo "Change this to 'etc/rc.d/init.d/...' !"
fi
+
+grep -r "^var/run//*" ./config/rootfiles/ >/dev/null 2>&1
+if [ "${?}" == "0" ]; then
+ echo "Error! 'var/run/...' in rootfiles files found!"
+ grep -r "^var/run//*" ./config/rootfiles/
+ echo "Comment this and create it at initskript if needed !"
+fi
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-07-17 5:00 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=20140717050032.8113E21001@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