From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. e0080803742226fed532dfead30c6f7d0d27e968
Date: Mon, 02 Jun 2014 18:05:44 +0200 [thread overview]
Message-ID: <20140602160544.CAB1B21C7E@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2444 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 e0080803742226fed532dfead30c6f7d0d27e968 (commit)
via d15e01a5ef5feb0f7ccc1b8b614137b2ba4ee670 (commit)
from 8bab8832b7b7e4d4367961bc30f89b3a7ff301c9 (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 e0080803742226fed532dfead30c6f7d0d27e968
Merge: d15e01a 8bab883
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Mon Jun 2 18:04:50 2014 +0200
Merge branch 'next' of ssh://git.ipfire.org/pub/git/ipfire-2.x into next
commit d15e01a5ef5feb0f7ccc1b8b614137b2ba4ee670
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Mon Jun 2 18:03:56 2014 +0200
kernel: update to 3.10.41.
-----------------------------------------------------------------------
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 9146ad9..a86dab6 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
include Config
-VER = 3.10.40
+VER = 3.10.41
RPI_PATCHES = linux-3.10.38-grsec-1b49b45
-GRS_PATCHES = grsecurity-2.9.1-3.10.40-ipfire1.patch.xz
+GRS_PATCHES = grsecurity-2.9.1-3.10.41-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 = 45
+PAK_VER = 46
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 = c1dca08f0f1a60f29b7caa9ff45582a8
+$(DL_FILE)_MD5 = 08631db3e6b4328b0315f59ef3fa7b0a
rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = a7408e8bad57b4b2cb677dd5a0bfb7ff
-$(GRS_PATCHES)_MD5 = f46506dd67e459fc41d60d0641323668
+$(GRS_PATCHES)_MD5 = de48891a35952a3c6de5beea694f7557
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-06-02 16:05 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=20140602160544.CAB1B21C7E@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