From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 9982e01913d0c098a2a184b84a8f4f8137166ecf
Date: Sun, 07 Dec 2014 20:48:57 +0100 [thread overview]
Message-ID: <20141207194857.6E02B2045F@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2583 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, master has been updated
via 9982e01913d0c098a2a184b84a8f4f8137166ecf (commit)
from bbdd37b1d57992649cfc1edac2f761ae2c520afb (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 9982e01913d0c098a2a184b84a8f4f8137166ecf
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Dec 7 20:48:32 2014 +0100
kernel: update to 3.14.26.
-----------------------------------------------------------------------
Summary of changes:
lfs/linux | 21 ++++++++++++---------
1 file changed, 12 insertions(+), 9 deletions(-)
Difference in files:
diff --git a/lfs/linux b/lfs/linux
index dac6275..25206ba 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,11 +24,11 @@
include Config
-VER = 3.14.25
+VER = 3.14.26
-RPI_PATCHES = 3.14.25-grsec-ipfire1
-A7M_PATCHES = 3.14.25-grsec-ipfire1
-GRS_PATCHES = grsecurity-3.0-3.14.25-201411220954.patch.xz
+RPI_PATCHES = 3.14.26-grsec-ipfire1
+A7M_PATCHES = 3.14.26-grsec-ipfire1
+GRS_PATCHES = grsecurity-3.0-3.14.26-201412071005.patch.xz
THISAPP = linux-$(VER)
DL_FILE = linux-$(VER).tar.xz
@@ -37,7 +37,7 @@ DIR_APP = $(DIR_SRC)/$(THISAPP)
CFLAGS =
CXXFLAGS =
-PAK_VER = 53
+PAK_VER = 54
DEPS = ""
VERSUFIX=ipfire$(KCFG)
@@ -77,10 +77,13 @@ rpi-patches-$(RPI_PATCHES).patch.xz = $(URL_IPFIRE)/rpi-patches-$(RPI_PATCHES).
arm7-multi-patches-$(A7M_PATCHES).patch.xz = $(URL_IPFIRE)/arm7-multi-patches-$(A7M_PATCHES).patch.xz
$(GRS_PATCHES) = $(URL_IPFIRE)/$(GRS_PATCHES)
-$(DL_FILE)_MD5 = 3ae910d35292706d85870c3939547123
-rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = b573af847c28ebed8c15a74542360db1
-arm7-multi-patches-$(A7M_PATCHES).patch.xz_MD5 = 8b47b81a530db68cb2c2f6bb6418ca28
-$(GRS_PATCHES)_MD5 = 6b2c8669e39304cfe647f9de16260929
+$(DL_FILE)_MD5 = 9a91a9c507c9efb68c7075e151c30fa7
+
+rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 543a77d5602829f78b18788e5cb82188
+
+arm7-multi-patches-$(A7M_PATCHES).patch.xz_MD5 = c395cb6c1946d1c0fb7edc66ea912e86
+
+$(GRS_PATCHES)_MD5 = d98e1c65baab50e6669616785dbc34e1
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-12-07 19:48 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=20141207194857.6E02B2045F@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