From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. c03e8bd6ef18c138b33b1eeadc95b397054ac76e
Date: Wed, 06 Jun 2018 06:29:23 +0100 [thread overview]
Message-ID: <20180606052924.428D21081DF2@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1812 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 c03e8bd6ef18c138b33b1eeadc95b397054ac76e (commit)
from 3da7324a721be7bc8f76e8b17068c18aeeae6bdd (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 c03e8bd6ef18c138b33b1eeadc95b397054ac76e
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Wed Jun 6 07:26:55 2018 +0200
kernel: update to 4.14.48
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 62c43aac0..de1b8285c 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,8 +24,8 @@
include Config
-VER = 4.14.47
-ARM_PATCHES = 4.14.47-ipfire0
+VER = 4.14.48
+ARM_PATCHES = 4.14.48-ipfire0
THISAPP = linux-$(VER)
DL_FILE = linux-$(VER).tar.xz
@@ -75,7 +75,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 = c998ebfbabfdc640060b28839a7a9fca
+$(DL_FILE)_MD5 = 417214059879164ab422fa359af80900
arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5 = 7c6e98b0514945a4e65e0c43b9920035
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-06-06 5:29 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=20180606052924.428D21081DF2@git01.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