From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. b843030f09722737b08cbfdd3371e2bd26923d6f
Date: Fri, 21 Jun 2013 20:03:42 +0200 [thread overview]
Message-ID: <20130621180400.C76302075C@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1630 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 b843030f09722737b08cbfdd3371e2bd26923d6f (commit)
from 4d638d5ec938a3e7ef11a49457d456b6b5a1b2e6 (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 b843030f09722737b08cbfdd3371e2bd26923d6f
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Jun 21 20:02:45 2013 +0200
core70: fix destroing the /etc/init.d symlink.
Never put /etc/init/* to a rootfile !!!
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/70/filelists/files | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/config/rootfiles/core/70/filelists/files b/config/rootfiles/core/70/filelists/files
index 52b9be7..1809e77 100644
--- a/config/rootfiles/core/70/filelists/files
+++ b/config/rootfiles/core/70/filelists/files
@@ -1,9 +1,9 @@
etc/system-release
etc/issue
+etc/rc.d/init.d/firewall
etc/rc.d/init.d/network-vlans
etc/rc.d/init.d/squid
usr/local/bin/openvpnctrl
-etc/init.d/firewall
srv/web/ipfire/cgi-bin/ddns.cgi
srv/web/ipfire/cgi-bin/proxy.cgi
usr/lib/squid/errors/tr/ERR_ACCESS_DENIED
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-06-21 18:03 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=20130621180400.C76302075C@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