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. 562e14b01f02f811ed4c5c98e563aa2de2d9caf4
Date: Fri, 20 Dec 2013 23:32:40 +0100	[thread overview]
Message-ID: <20131220223244.B7975205E4@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1973 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  562e14b01f02f811ed4c5c98e563aa2de2d9caf4 (commit)
      from  3c037075d0f6c296225500651d89b03b3c65d9e2 (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 562e14b01f02f811ed4c5c98e563aa2de2d9caf4
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Fri Dec 20 23:31:40 2013 +0100

    kernel: update to 3.10.25.

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

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 56d94a9..080e801 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
 
 include Config
 
-VER        = 3.10.24
+VER        = 3.10.25
 
 RPI_PATCHES = linux-3.10.10-grsec-c1af7c6
-GRS_PATCHES = grsecurity-2.9.1-3.10.24-ipfire1.patch.xz
+GRS_PATCHES = grsecurity-2.9.1-3.10.25-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				= 4b1270dda167a0ee8bead2681e0a9965
+$(DL_FILE)_MD5				= 762a030e6b927d855a7da3599381d6ee
 rpi-patches-$(RPI_PATCHES).patch.xz_MD5	= f55981853573236069db5ad9fb7a4bd9
-$(GRS_PATCHES)_MD5			= c312b94bea5dc1f489451e856590a573
+$(GRS_PATCHES)_MD5			= 3fa426c36c1faab3262ff68f166dbae2
 
 install : $(TARGET)
 


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

                 reply	other threads:[~2013-12-20 22:32 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=20131220223244.B7975205E4@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