From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 6f49e32b74ba5312385238e6b59bbe2f52ea2e5a
Date: Sat, 12 Oct 2013 14:24:35 +0200 [thread overview]
Message-ID: <20131012122436.16677208D8@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1374 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 6f49e32b74ba5312385238e6b59bbe2f52ea2e5a (commit)
from 0e4f36aee459a4e4f7dca4037c8bbdc181d74836 (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 6f49e32b74ba5312385238e6b59bbe2f52ea2e5a
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Sat Oct 12 13:26:53 2013 +0200
squid: Enable netfilter transparent mode.
-----------------------------------------------------------------------
Summary of changes:
lfs/squid | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Difference in files:
diff --git a/lfs/squid b/lfs/squid
index 2e3fd3d..bc0ef71 100644
--- a/lfs/squid
+++ b/lfs/squid
@@ -114,7 +114,7 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
--enable-cache-digests \
--enable-forw-via-db \
--enable-htcp \
- --enable-ipf-transparent \
+ --enable-linux-netfilter \
--enable-kill-parent-hack \
--disable-wccpv2 \
--enable-icap-client \
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-10-12 12:24 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=20131012122436.16677208D8@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