From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 57d98918a1a11077d8d3e3caeaca9d85e4200ea5
Date: Fri, 29 Jan 2016 14:25:59 +0100 [thread overview]
Message-ID: <20160129132600.0C94221497@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2263 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 57d98918a1a11077d8d3e3caeaca9d85e4200ea5 (commit)
from 35b24ff8a933e2ab8614c4f9b7c27c25c6f95473 (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 57d98918a1a11077d8d3e3caeaca9d85e4200ea5
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Jan 29 14:25:25 2016 +0100
kernel: update to 3.14.60
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/linux | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
Difference in files:
diff --git a/lfs/linux b/lfs/linux
index 7825322..ce4553e 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
include Config
-VER = 3.14.59
-RPI_PATCHES = 3.14.59-grsec-ipfire1
-A7M_PATCHES = 3.14.59-grsec-ipfire1
-GRS_PATCHES = grsecurity-3.1ipfire-3.14.59-v1.patch.xz
+VER = 3.14.60
+RPI_PATCHES = 3.14.60-grsec-ipfire1
+A7M_PATCHES = 3.14.60-grsec-ipfire1
+GRS_PATCHES = grsecurity-3.1ipfire-3.14.60-v1.patch.xz
THISAPP = linux-$(VER)
@@ -83,11 +83,10 @@ 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 = 9e3fbdf5067ffc413c0effc427050112
+$(DL_FILE)_MD5 = 25d623a8a884d055313e16aec59fdd7a
rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = ed11c924a484646018be8671935407d0
arm7-multi-patches-$(A7M_PATCHES).patch.xz_MD5 = eafe3ef25946d9d5169dd5af4d280ba5
-$(GRS_PATCHES)_MD5 = 63721b2131356a614edcb4d00a64e62e
-
+$(GRS_PATCHES)_MD5 = 1b6941fd7cea95acce6575917ed08a31
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-01-29 13:25 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=20160129132600.0C94221497@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