From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 4d9e31ab78dbcf8d6c7cd5720d7cdf410281d778
Date: Thu, 16 Apr 2015 20:53:10 +0200 [thread overview]
Message-ID: <20150416185310.C7DE021AD0@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2400 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 4d9e31ab78dbcf8d6c7cd5720d7cdf410281d778 (commit)
from 30986dbf03b2ce231f3a53989d4d81ec7ccb1681 (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 4d9e31ab78dbcf8d6c7cd5720d7cdf410281d778
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Apr 16 20:52:44 2015 +0200
kernel: update to 3.14.38
-----------------------------------------------------------------------
Summary of changes:
lfs/linux | 16 ++++++++--------
1 file changed, 8 insertions(+), 8 deletions(-)
Difference in files:
diff --git a/lfs/linux b/lfs/linux
index 7ac13d6..300fd87 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,11 +24,11 @@
include Config
-VER = 3.14.37
+VER = 3.14.38
-RPI_PATCHES = 3.14.37-grsec-ipfire1
-A7M_PATCHES = 3.14.37-grsec-ipfire1
-GRS_PATCHES = grsecurity-3.1-3.14.37-201503270048.patch.xz
+RPI_PATCHES = 3.14.38-grsec-ipfire1
+A7M_PATCHES = 3.14.38-grsec-ipfire1
+GRS_PATCHES = grsecurity-3.1-3.14.38-201504142259.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 = 43abcb454054c53fb07296e84119edc5
-rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 375dc501711ff3ffeffdfc9848675d26
-arm7-multi-patches-$(A7M_PATCHES).patch.xz_MD5 = 8a0a0d6ef78d53b3095691499dac4b71
-$(GRS_PATCHES)_MD5 = d83ca635c83bbd5efc4372992ab58094
+$(DL_FILE)_MD5 = c4d0154627e02dc43c67fa616ff1e569
+rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = e423c8b3a408f23b9a26f8f0f4384c50
+arm7-multi-patches-$(A7M_PATCHES).patch.xz_MD5 = a4a4103255e93bfcb02652212b0ae3fc
+$(GRS_PATCHES)_MD5 = 6d6ed13c08ae96f6470c30c00e08b130
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-04-16 18:53 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=20150416185310.C7DE021AD0@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