public inbox for ipfire-scm@lists.ipfire.org
 help / color / mirror / Atom feed
From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. b10365c832420b09be9cb62161fa21aef89e4017
Date: Sat, 22 Jun 2019 15:01:31 +0100	[thread overview]
Message-ID: <20190622140132.0DA3C80F69A@people01.i.ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2114 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  b10365c832420b09be9cb62161fa21aef89e4017 (commit)
       via  8c261d91e87a73804d11d71279ea103a4ac99fd6 (commit)
      from  c6e032e13d5d1eff16189c50229f00522835aae5 (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 b10365c832420b09be9cb62161fa21aef89e4017
Merge: 8c261d91e c6e032e13
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sat Jun 22 16:01:16 2019 +0200

    Merge branch 'next' of git.ipfire.org:/pub/git/ipfire-2.x into next

commit 8c261d91e87a73804d11d71279ea103a4ac99fd6
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date:   Sat Jun 22 16:00:37 2019 +0200

    kernel: 4.14.129
    
    Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>

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

Summary of changes:
 lfs/linux | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

Difference in files:
diff --git a/lfs/linux b/lfs/linux
index 6669cf220..91b014983 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,8 +24,8 @@
 
 include Config
 
-VER         = 4.14.128
-ARM_PATCHES = 4.14.128-ipfire0
+VER         = 4.14.129
+ARM_PATCHES = 4.14.129-ipfire0
 
 THISAPP    = linux-$(VER)
 DL_FILE    = linux-$(VER).tar.xz
@@ -82,7 +82,7 @@ objects =$(DL_FILE) \
 $(DL_FILE)					= $(URL_IPFIRE)/$(DL_FILE)
 arm-multi-patches-$(ARM_PATCHES).patch.xz	= $(URL_IPFIRE)/arm-multi-patches-$(ARM_PATCHES).patch.xz
 
-$(DL_FILE)_MD5					= 6c51d852170552a503b497766cfb632f
+$(DL_FILE)_MD5					= e21f063410d670641b22512ae5219cd0
 arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5	= 5c5f6da89606e63701cdcd84a500aca1
 
 install : $(TARGET)


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

                 reply	other threads:[~2019-06-22 14:01 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=20190622140132.0DA3C80F69A@people01.i.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