From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 346d838ba8a86200a974674e994344979fb122db
Date: Mon, 09 Feb 2015 07:53:42 +0100 [thread overview]
Message-ID: <20150209065343.24D96221FB@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2316 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, master has been updated
via 346d838ba8a86200a974674e994344979fb122db (commit)
from f1ce93f422aca7934d88c358b34a3a7da5d8ab99 (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 346d838ba8a86200a974674e994344979fb122db
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Feb 8 22:36:02 2015 +0100
kernel: update to 3.14.32.
-----------------------------------------------------------------------
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 6ae69ed..c6ca774 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,11 +24,11 @@
include Config
-VER = 3.14.31
+VER = 3.14.32
-RPI_PATCHES = 3.14.31-grsec-ipfire1
-A7M_PATCHES = 3.14.31-grsec-ipfire1
-GRS_PATCHES = grsecurity-3.0-3.14.31-201501310705.patch.xz
+RPI_PATCHES = 3.14.32-grsec-ipfire1
+A7M_PATCHES = 3.14.32-grsec-ipfire1
+GRS_PATCHES = grsecurity-3.0-3.14.32-201502062101.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 = f37ac2b5675ac59e46103f81e5f31624
-rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 6c18ea5fb919e09e821b9b2018a7f93e
+$(DL_FILE)_MD5 = 3178fb8f6f1eafcffdd730fec68754f8
+rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 375dc501711ff3ffeffdfc9848675d26
arm7-multi-patches-$(A7M_PATCHES).patch.xz_MD5 = efcfe5889f120d879387dd4ebe881587
-$(GRS_PATCHES)_MD5 = af534d3efa6926fa2d88d9dcaec8462f
+$(GRS_PATCHES)_MD5 = c1565eb2a630a673f3ace31a6901e251
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2015-02-09 6: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=20150209065343.24D96221FB@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