From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 1c38ad92a274423e36e085b69bea0951889d35b4
Date: Fri, 07 Feb 2014 23:03:41 +0100 [thread overview]
Message-ID: <20140207220356.3765E20C37@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2138 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 1c38ad92a274423e36e085b69bea0951889d35b4 (commit)
from f17f51e87361efe5c687690e0614636384657b9d (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 1c38ad92a274423e36e085b69bea0951889d35b4
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Feb 7 20:16:35 2014 +0100
kernel: update to 3.10.29.
-----------------------------------------------------------------------
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 274657c..6b7e9b8 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
include Config
-VER = 3.10.28
+VER = 3.10.29
RPI_PATCHES = linux-3.10.27-grsec-943b563
-GRS_PATCHES = grsecurity-2.9.1-3.10.28-ipfire1.patch.xz
+GRS_PATCHES = grsecurity-2.9.1-3.10.29-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 = 33
+PAK_VER = 34
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 = 789a39e8a381a60e46fe922cb66d77e2
+$(DL_FILE)_MD5 = 59e4f495b1302f2bca0e72d204c5fd0b
rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = 8cf81f48408306d93ccee59b58af2e92
-$(GRS_PATCHES)_MD5 = ebbcee19d1231da81f7238de703ff911
+$(GRS_PATCHES)_MD5 = b39b69eb7439141621ecf0221b3bd29e
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-02-07 22:03 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=20140207220356.3765E20C37@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