From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 57e527c84a4e3952c7842637e2e4b6f252394de2
Date: Wed, 29 Apr 2015 19:42:30 +0200 [thread overview]
Message-ID: <20150429174230.5051F21A84@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2314 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 57e527c84a4e3952c7842637e2e4b6f252394de2 (commit)
from 6caea1086d15a0f6d797da31a67d132a298c5d14 (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 57e527c84a4e3952c7842637e2e4b6f252394de2
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Apr 29 19:42:06 2015 +0200
kernel: update to 3.14.40
-----------------------------------------------------------------------
Summary of changes:
lfs/linux | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
Difference in files:
diff --git a/lfs/linux b/lfs/linux
index 8b4f941..a68dda7 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,11 +24,11 @@
include Config
-VER = 3.14.39
+VER = 3.14.40
-RPI_PATCHES = 3.14.39-grsec-ipfire1
-A7M_PATCHES = 3.14.39-grsec-ipfire1
-GRS_PATCHES = grsecurity-3.1-3.14.39-201504190814.patch.xz
+RPI_PATCHES = 3.14.40-grsec-ipfire1
+A7M_PATCHES = 3.14.40-grsec-ipfire1
+GRS_PATCHES = grsecurity-3.1-3.14.40-201504290821.patch.xz
THISAPP = linux-$(VER)
DL_FILE = linux-$(VER).tar.xz
@@ -77,10 +77,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 = 3581855d0dbfcbe1140dfcd1406d0a91
-rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 5056304af0a199194abd0bcb00015f28
+$(DL_FILE)_MD5 = 8a66901cdcce5b2650672af41ad4a9fd
+rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 375dc501711ff3ffeffdfc9848675d26
arm7-multi-patches-$(A7M_PATCHES).patch.xz_MD5 = a4a4103255e93bfcb02652212b0ae3fc
-$(GRS_PATCHES)_MD5 = 2121d0bf825da9ff6321e2940f247c5e
+$(GRS_PATCHES)_MD5 = 52d5d8dae26f4c1fd1c8d67268260bdd
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-04-29 17:42 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=20150429174230.5051F21A84@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