From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 8080197b129b82c93dffc77b970aa7028c0ba4a0
Date: Fri, 11 May 2018 07:43:27 +0100 [thread overview]
Message-ID: <20180511064328.428001081DF2@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1813 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 8080197b129b82c93dffc77b970aa7028c0ba4a0 (commit)
from a305ffea8bf2df76d753a63ca93af019413a3d72 (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 8080197b129b82c93dffc77b970aa7028c0ba4a0
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Thu May 10 21:34:07 2018 +0200
kernel: update to 4.14.40
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 646d7256a..76e847813 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,8 +24,8 @@
include Config
-VER = 4.14.39
-ARM_PATCHES = 4.14.39-ipfire0
+VER = 4.14.40
+ARM_PATCHES = 4.14.40-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 = cbb2a17f13f12e4dfe1ed20a23d53ef4
+$(DL_FILE)_MD5 = 8376ed89777760443a359edb1d08ed9a
arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5 = ae7091bb79bad05c8394c8bacc48dd60
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-05-11 6:43 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=20180511064328.428001081DF2@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