From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. 8e05d968962afc0cb7784d65e0e8fe80bd945e1a
Date: Fri, 04 Apr 2014 13:54:07 +0200 [thread overview]
Message-ID: <20140404115423.0C42220C44@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2140 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 8e05d968962afc0cb7784d65e0e8fe80bd945e1a (commit)
from 51e7782863d52fca2f38971292ae54860e2aaf98 (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 8e05d968962afc0cb7784d65e0e8fe80bd945e1a
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Apr 4 13:53:41 2014 +0200
kernel: update to 3.10.36.
-----------------------------------------------------------------------
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 4d5ebf8..e5f12d2 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
include Config
-VER = 3.10.35
+VER = 3.10.36
RPI_PATCHES = linux-3.10.34-grsec-dea8280
-GRS_PATCHES = grsecurity-2.9.1-3.10.35-ipfire1.patch.xz
+GRS_PATCHES = grsecurity-2.9.1-3.10.36-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 = 40
+PAK_VER = 41
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 = 50fb4fb277eedd0de692e2754aec878a
+$(DL_FILE)_MD5 = 721f76050755ec8ec88876ee350a2726
rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 522683db031f7033b1b5dfe1b1f30e67
-$(GRS_PATCHES)_MD5 = e6e79d8b015692ad3f47968c2b275938
+$(GRS_PATCHES)_MD5 = 85717c4d6643ea52eef443ee7bc873e2
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-04-04 11:54 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=20140404115423.0C42220C44@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