From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 43747fae333273890aadb66b72d911efaa4c2086
Date: Fri, 26 Feb 2016 13:24:23 +0000 [thread overview]
Message-ID: <20160226132423.A20291081BC7@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 43747fae333273890aadb66b72d911efaa4c2086 (commit)
from 5f39eb211974f1fa21c1f769f62b779f85ffbdf4 (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 43747fae333273890aadb66b72d911efaa4c2086
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Feb 26 13:43:33 2016 +0100
kernel: update to 3.14.62
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 e599360..262e591 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
include Config
-VER = 3.14.61
-RPI_PATCHES = 3.14.61-grsec-ipfire1
-A7M_PATCHES = 3.14.61-grsec-ipfire1
-GRS_PATCHES = grsecurity-3.1ipfire-3.14.61-v1.patch.xz
+VER = 3.14.62
+RPI_PATCHES = 3.14.62-grsec-ipfire1
+A7M_PATCHES = 3.14.62-grsec-ipfire1
+GRS_PATCHES = grsecurity-3.1ipfire-3.14.62-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 = 7aa25fc3aa75c3043d03b0e0e24024d4
+$(DL_FILE)_MD5 = 84dd675bb2024beb18ade2fe55e7b47d
rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 6f84442e9c00aab43e8118db199107c4
arm7-multi-patches-$(A7M_PATCHES).patch.xz_MD5 = 4ed04c218c0a84a6a1954d220ad601b6
-$(GRS_PATCHES)_MD5 = 30b815156fa714a95c28e02cbbcf7904
+$(GRS_PATCHES)_MD5 = 9a77776b2740084dc80846e707bca0e3
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2016-02-26 13: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=20160226132423.A20291081BC7@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