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, master, updated. 6e283deb2dcc9039a5966ab21033bf06574ce65e
Date: Tue, 06 May 2014 18:31:26 +0200	[thread overview]
Message-ID: <20140506163129.1340820836@argus.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2140 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, master has been updated
       via  6e283deb2dcc9039a5966ab21033bf06574ce65e (commit)
      from  b7265a986650019e19f37ffe729062005a4a6ea6 (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 6e283deb2dcc9039a5966ab21033bf06574ce65e
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Tue May 6 18:30:51 2014 +0200

    kernel: update to 3.10.39.

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

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 c1d794a..e6ac36c 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,10 +24,10 @@
 
 include Config
 
-VER        = 3.10.38
+VER        = 3.10.39
 
 RPI_PATCHES = linux-3.10.38-grsec-1b49b45
-GRS_PATCHES = grsecurity-2.9.1-3.10.38-ipfire1.patch.xz
+GRS_PATCHES = grsecurity-2.9.1-3.10.39-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    = 43
+PAK_VER    = 44
 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				= cef991f05d2d1a15f08ca88ac31ee83e
+$(DL_FILE)_MD5				= 74db7cc558a1a72ebf5044d286e2bc47
 rpi-patches-$(RPI_PATCHES).patch.xz_MD5	= a7408e8bad57b4b2cb677dd5a0bfb7ff
-$(GRS_PATCHES)_MD5			= a50ac65d64c72badd21695c2294f8548
+$(GRS_PATCHES)_MD5			= 6296b7ec4146544249075249e338ceb3
 
 install : $(TARGET)
 


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

                 reply	other threads:[~2014-05-06 16:31 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=20140506163129.1340820836@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