From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. f3b0222e3f85921f3792b03a2428f611c50b339c
Date: Wed, 09 Jan 2013 12:39:59 +0100 [thread overview]
Message-ID: <20130109114000.1D8D9200DA@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1937 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 f3b0222e3f85921f3792b03a2428f611c50b339c (commit)
from b25c4ede55e33e6add1690940ddade495d71b8d1 (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 f3b0222e3f85921f3792b03a2428f611c50b339c
Author: Michael Tremer <michael.tremer(a)ipfire.org>
Date: Wed Jan 9 12:39:16 2013 +0100
squid: Update to 3.1.22.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/{oldcore/32 => core/66}/filelists/squid | 0
lfs/squid | 4 ++--
2 files changed, 2 insertions(+), 2 deletions(-)
copy config/rootfiles/{oldcore/32 => core/66}/filelists/squid (100%)
Difference in files:
diff --git a/config/rootfiles/core/66/filelists/squid b/config/rootfiles/core/66/filelists/squid
new file mode 120000
index 0000000..2dc8372
--- /dev/null
+++ b/config/rootfiles/core/66/filelists/squid
@@ -0,0 +1 @@
+../../../common/squid
\ No newline at end of file
diff --git a/lfs/squid b/lfs/squid
index 7468328..7c0c5c9 100644
--- a/lfs/squid
+++ b/lfs/squid
@@ -24,7 +24,7 @@
include Config
-VER = 3.1.20
+VER = 3.1.22
THISAPP = squid-$(VER)
DL_FILE = $(THISAPP).tar.bz2
@@ -40,7 +40,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = c4d733a383c0508fd0746d64a2d7278a
+$(DL_FILE)_MD5 = a25ce5937875990c950cc8cd1b120a5e
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-01-09 11:39 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=20130109114000.1D8D9200DA@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