From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, master, updated. ac28974f043769f6cf55d9b276b9beab67911e62
Date: Sun, 27 Apr 2014 11:37:46 +0200 [thread overview]
Message-ID: <20140427093746.9C48720A85@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2141 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 ac28974f043769f6cf55d9b276b9beab67911e62 (commit)
from bf3662157a496e5e410fc9dc47d8dfbe64bf7abd (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 ac28974f043769f6cf55d9b276b9beab67911e62
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun Apr 27 11:37:14 2014 +0200
kernel: update to 3.10.38.
-----------------------------------------------------------------------
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 bf04240..8f78d13 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
include Config
-VER = 3.10.37
+VER = 3.10.38
RPI_PATCHES = linux-3.10.34-grsec-dea8280
-GRS_PATCHES = grsecurity-2.9.1-3.10.37-ipfire1.patch.xz
+GRS_PATCHES = grsecurity-2.9.1-3.10.38-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 = 42
+PAK_VER = 43
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 = a08a10ffc31b07d9422af1cd2baa3274
+$(DL_FILE)_MD5 = cef991f05d2d1a15f08ca88ac31ee83e
rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 522683db031f7033b1b5dfe1b1f30e67
-$(GRS_PATCHES)_MD5 = 7b0f44571974217d79dbcdf5d7e33976
+$(GRS_PATCHES)_MD5 = a50ac65d64c72badd21695c2294f8548
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-04-27 9:37 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=20140427093746.9C48720A85@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