From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. af578bab4599d5e9fe57aff7e6636e47ffcd2edd
Date: Thu, 22 Aug 2013 17:27:28 +0200 [thread overview]
Message-ID: <20130822152728.F3F4720287@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2173 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 af578bab4599d5e9fe57aff7e6636e47ffcd2edd (commit)
via 6c00bad302384208e825d0fd7c7ce332d6231219 (commit)
from e65fe151a5b7bf7df9525fcae1cb920667818c2a (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 af578bab4599d5e9fe57aff7e6636e47ffcd2edd
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Aug 22 17:27:13 2013 +0200
squid: Update rootfile.
commit 6c00bad302384208e825d0fd7c7ce332d6231219
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Thu Aug 22 17:26:23 2013 +0200
tor: Rootfile update.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/common/squid | 1 +
config/rootfiles/packages/tor | 3 +++
2 files changed, 4 insertions(+)
Difference in files:
diff --git a/config/rootfiles/common/squid b/config/rootfiles/common/squid
index 15c921f..9515dc3 100644
--- a/config/rootfiles/common/squid
+++ b/config/rootfiles/common/squid
@@ -1824,6 +1824,7 @@ usr/lib/squid/errors/tr/ERR_AGENT_WPAD
usr/lib/squid/errors/tr/ERR_CACHE_ACCESS_DENIED
usr/lib/squid/errors/tr/ERR_CACHE_MGR_ACCESS_DENIED
usr/lib/squid/errors/tr/ERR_CANNOT_FORWARD
+usr/lib/squid/errors/tr/ERR_CONFLICT_HOST
usr/lib/squid/errors/tr/ERR_CONNECT_FAIL
usr/lib/squid/errors/tr/ERR_DIR_LISTING
usr/lib/squid/errors/tr/ERR_DNS_FAIL
diff --git a/config/rootfiles/packages/tor b/config/rootfiles/packages/tor
index 8eb6dad..58de7da 100644
--- a/config/rootfiles/packages/tor
+++ b/config/rootfiles/packages/tor
@@ -1,6 +1,9 @@
#etc/logrotate.d
etc/logrotate.d/tor
etc/rc.d/init.d/tor
+etc/rc.d/rc0.d/K40tor
+etc/rc.d/rc3.d/S60tor
+etc/rc.d/rc6.d/K40tor
#etc/tor
etc/tor/tor-tsocks.conf
etc/tor/torrc
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-08-22 15:27 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=20130822152728.F3F4720287@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