From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. f763ff3224dec67963bd47ef176085d7dd310fc0
Date: Mon, 24 Mar 2014 13:29:03 +0100 [thread overview]
Message-ID: <20140324122910.B05F720C37@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2139 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 f763ff3224dec67963bd47ef176085d7dd310fc0 (commit)
from af433268e063cbcb435b4770027906d897d9bb6f (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 f763ff3224dec67963bd47ef176085d7dd310fc0
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Mon Mar 24 13:28:29 2014 +0100
kernel: update to 3.10.34.
-----------------------------------------------------------------------
Summary of changes:
lfs/linux | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
Difference in files:
diff --git a/lfs/linux b/lfs/linux
index 687de36..9f82ab0 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
include Config
-VER = 3.10.33
+VER = 3.10.34
RPI_PATCHES = linux-3.10.27-grsec-943b563
-GRS_PATCHES = grsecurity-2.9.1-3.10.33-ipfire1.patch.xz
+GRS_PATCHES = grsecurity-2.9.1-3.10.34-ipfire1.patch.xz
THISAPP = linux-$(VER)
DL_FILE = linux-$(VER).tar.xz
@@ -36,7 +36,7 @@ DIR_APP = $(DIR_SRC)/$(THISAPP)
CFLAGS =
CXXFLAGS =
-PAK_VER = 38
+PAK_VER = 39
DEPS = ""
VERSUFIX=ipfire$(KCFG)
@@ -74,9 +74,9 @@ $(DL_FILE) = $(URL_IPFIRE)/$(DL_FILE)
rpi-patches-$(RPI_PATCHES).patch.xz = $(URL_IPFIRE)/rpi-patches-$(RPI_PATCHES).patch.xz
$(GRS_PATCHES) = $(URL_IPFIRE)/$(GRS_PATCHES)
-$(DL_FILE)_MD5 = 01865f9c129f3c7eee51e25b3781a364
+$(DL_FILE)_MD5 = 30991b495a3d75196d5608072d2e62e6
rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 8cf81f48408306d93ccee59b58af2e92
-$(GRS_PATCHES)_MD5 = c99be0018e8bc55fb2e2b8f0ea9783d5
+$(GRS_PATCHES)_MD5 = b490f7f3bf48387ab2eb60212fcf0c11
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-03-24 12:29 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=20140324122910.B05F720C37@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