public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, fifteen, updated. e99dcbdbab9ae7a301d8a4871c18bc81fe5469c8
Date: Fri, 29 Nov 2013 23:56:20 +0100	[thread overview]
Message-ID: <20131129225632.B4A9B21550@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1967 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  e99dcbdbab9ae7a301d8a4871c18bc81fe5469c8 (commit)
      from  35ca8e0203c4d94178f2186d0c0b73f8ec48bc50 (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 e99dcbdbab9ae7a301d8a4871c18bc81fe5469c8
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Fri Nov 29 23:37:39 2013 +0100

    kernel: update to 3.10.21.

-----------------------------------------------------------------------

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 ca1b8cb..ddc8b64 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
 
 include Config
 
-VER        = 3.10.20
+VER        = 3.10.21
 
 RPI_PATCHES = linux-3.10.10-c1af7c6
-GRS_PATCHES = grsecurity-2.9.1-3.10.20-ipfire1.patch.xz
+GRS_PATCHES = grsecurity-2.9.1-3.10.21-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				= 96031ef7d952a318cc13a95217a6939b
+$(DL_FILE)_MD5				= dc5f31aef4aac0cc271e7ecf1a4b485d
 rpi-patches-$(RPI_PATCHES).patch.xz_MD5	= ef9274b3ff5d05daaaa4bdbe86ad00fc
-$(GRS_PATCHES)_MD5			= 85971c7eacaa1976c1b8aa0f7a071e09
+$(GRS_PATCHES)_MD5			= 00682f22ea21f49965ed653025fb30b5
 
 install : $(TARGET)
 


hooks/post-receive
--
IPFire 2.x development tree

                 reply	other threads:[~2013-11-29 22:56 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=20131129225632.B4A9B21550@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