From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, fifteen, updated. 278280da9606d394ec7c39127ffadc26a5a3d3d0
Date: Sat, 19 Oct 2013 15:06:43 +0200 [thread overview]
Message-ID: <20131019130643.C25CF207AE@argus.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2280 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, fifteen has been updated
via 278280da9606d394ec7c39127ffadc26a5a3d3d0 (commit)
via add7654e19ba28b6e7e3a38bf7ddbecd77909551 (commit)
from b64c3fc8a3cc9f789348d331d1e4ba78a032f612 (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 278280da9606d394ec7c39127ffadc26a5a3d3d0
Merge: add7654 b64c3fc
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Oct 19 15:05:42 2013 +0200
Merge branch 'fifteen' of ssh://git.ipfire.org/pub/git/ipfire-2.x into fifteen
commit add7654e19ba28b6e7e3a38bf7ddbecd77909551
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sat Oct 19 15:05:14 2013 +0200
kernel: update to 3.10.17.
-----------------------------------------------------------------------
Summary of changes:
lfs/linux | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
Difference in files:
diff --git a/lfs/linux b/lfs/linux
index d6a8b1d..0c8ac9f 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
include Config
-VER = 3.10.16
+VER = 3.10.17
RPI_PATCHES = linux-3.10.10-c1af7c6
-GRS_PATCHES = grsecurity-2.9.1-3.10.16-ipfire1.patch.xz
+GRS_PATCHES = grsecurity-2.9.1-3.10.17-ipfire1.patch.xz
THISAPP = linux-$(VER)
DL_FILE = linux-$(VER).tar.xz
@@ -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 = 5e232365cbc0797b716b605a165703e1
+$(DL_FILE)_MD5 = 0c52d1266fe1087bcfa6517646188ecc
rpi-patches-$(RPI_PATCHES).patch.xz_MD5 = ef9274b3ff5d05daaaa4bdbe86ad00fc
-$(GRS_PATCHES)_MD5 = 826d8a90e7cdfc84ac871512c773d712
+$(GRS_PATCHES)_MD5 = 2c005d8f5e55da2f23cb92af3baa7108
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2013-10-19 13:06 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=20131019130643.C25CF207AE@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