From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 1775dbd2c6dc36e26712bbffa593e12af475c6a2
Date: Thu, 10 Mar 2016 22:10:06 +0000 [thread overview]
Message-ID: <20160310221007.5B8D61081BC7@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2259 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 1775dbd2c6dc36e26712bbffa593e12af475c6a2 (commit)
from 46ce813e330925e0ab5969cf3e34c9e49fb9df88 (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 1775dbd2c6dc36e26712bbffa593e12af475c6a2
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Mar 10 22:29:02 2016 +0100
kernel: update to 3.14.64
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
lfs/linux | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
Difference in files:
diff --git a/lfs/linux b/lfs/linux
index b0c2635..5ca704d 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
include Config
-VER = 3.14.63
-RPI_PATCHES = 3.14.63-grsec-ipfire1
-A7M_PATCHES = 3.14.63-grsec-ipfire1
-GRS_PATCHES = grsecurity-3.1ipfire-3.14.63-v1.patch.xz
+VER = 3.14.64
+RPI_PATCHES = 3.14.64-grsec-ipfire1
+A7M_PATCHES = 3.14.64-grsec-ipfire1
+GRS_PATCHES = grsecurity-3.1ipfire-3.14.64-v1.patch.xz
THISAPP = linux-$(VER)
@@ -83,10 +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 = 6cf8a6b23849f47f511e0e46cfdb6392
+$(DL_FILE)_MD5 = d68173a31fb60e2195a4015fe1f83e97
rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 0d1059c18f4810abbe9aafb6beab445b
arm7-multi-patches-$(A7M_PATCHES).patch.xz_MD5 = 589eb8703fa2ba2944b2f925b7f7ffb3
-$(GRS_PATCHES)_MD5 = e84b05c9083fa0eb6bb49facd4f841dc
+$(GRS_PATCHES)_MD5 = 209ff5232dc4141789bc90f34b87d906
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-03-10 22:10 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=20160310221007.5B8D61081BC7@git01.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