From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 055ed1ffc99100f7c209aa96f1787325be9063c8
Date: Thu, 16 Jan 2014 13:42:11 +0100 [thread overview]
Message-ID: <20140116124224.ACDDF20ABF@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2616 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 055ed1ffc99100f7c209aa96f1787325be9063c8 (commit)
from 03e7b65b0173ae1ee9e3a5f326eef04596da3b14 (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 055ed1ffc99100f7c209aa96f1787325be9063c8
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu Jan 16 13:24:00 2014 +0100
kernel: update to 3.10.27.
-----------------------------------------------------------------------
Summary of changes:
config/rootfiles/core/76/update.sh | 2 +-
lfs/linux | 10 +++++-----
2 files changed, 6 insertions(+), 6 deletions(-)
Difference in files:
diff --git a/config/rootfiles/core/76/update.sh b/config/rootfiles/core/76/update.sh
index 1a3c6b3..8f0f0fd 100644
--- a/config/rootfiles/core/76/update.sh
+++ b/config/rootfiles/core/76/update.sh
@@ -71,7 +71,7 @@ esac
#
#
-KVER="3.10.26"
+KVER="3.10.27"
MOUNT=`grep "kernel" /boot/grub/grub.conf 2>/dev/null | tail -n 1 `
# Nur den letzten Parameter verwenden
echo $MOUNT > /dev/null
diff --git a/lfs/linux b/lfs/linux
index 560be5d..68e91d4 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
include Config
-VER = 3.10.26
+VER = 3.10.27
RPI_PATCHES = linux-3.10.10-grsec-c1af7c6
-GRS_PATCHES = grsecurity-2.9.1-3.10.26-ipfire1.patch.xz
+GRS_PATCHES = grsecurity-2.9.1-3.10.27-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 = 31
+PAK_VER = 32
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 = 9cdbcb3463b9753fafd97cddb38d1211
+$(DL_FILE)_MD5 = 4edaaea57dc940969c54ac249e49f7e7
rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = f55981853573236069db5ad9fb7a4bd9
-$(GRS_PATCHES)_MD5 = 1516189415141aa55eacb0a078e8909c
+$(GRS_PATCHES)_MD5 = a83aad5c389ea9a496ba41608267d3dc
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2014-01-16 12:42 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=20140116124224.ACDDF20ABF@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