From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. c24eba27a0d17acf40955e1fa58ae1aa8cc10175
Date: Mon, 02 Jun 2014 18:10:04 +0200 [thread overview]
Message-ID: <20140602161005.00DDD21C7E@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1507 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 c24eba27a0d17acf40955e1fa58ae1aa8cc10175 (commit)
from e0080803742226fed532dfead30c6f7d0d27e968 (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 c24eba27a0d17acf40955e1fa58ae1aa8cc10175
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Mon Jun 2 18:09:50 2014 +0200
core78: Reflect chnages about the ping command.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/78/update.sh | 4 ++++
1 file changed, 4 insertions(+)
Difference in files:
diff --git a/config/rootfiles/core/78/update.sh b/config/rootfiles/core/78/update.sh
index cb9af9f..6564379 100644
--- a/config/rootfiles/core/78/update.sh
+++ b/config/rootfiles/core/78/update.sh
@@ -165,6 +165,10 @@ if [ $BOOTSPACE -lt 1000 ]; then
esac
fi
+# Update ping
+rm -f /bin/ping
+ln -sf ../usr/bin/ping /bin/ping
+chmod 4755 /usr/bin/ping
# Update Language cache
perl -e "require '/var/ipfire/lang.pl'; &Lang::BuildCacheLang"
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-06-02 16:10 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=20140602161005.00DDD21C7E@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