From: git@ipfire.org
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. fc6df72e6ea9b1f93fa05af5029ce9b649624702
Date: Sun, 27 May 2018 15:09:19 +0100 [thread overview]
Message-ID: <20180527140919.D99841081DF2@git01.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2207 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 fc6df72e6ea9b1f93fa05af5029ce9b649624702 (commit)
via c256f0160822324c20ddb87d82a8bdfe1ec98e50 (commit)
from 7039d8ae91ee7cca211e4a6be8cf9012c97d4a5d (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 fc6df72e6ea9b1f93fa05af5029ce9b649624702
Merge: c256f0160 7039d8ae9
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun May 27 16:07:07 2018 +0200
Merge branch 'next' of git.ipfire.org:/pub/git/ipfire-2.x into next
commit c256f0160822324c20ddb87d82a8bdfe1ec98e50
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Sun May 27 16:06:25 2018 +0200
kernel: update to 4.14.44
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
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 a65be9190..1b5e91253 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,8 +24,8 @@
include Config
-VER = 4.14.43
-ARM_PATCHES = 4.14.43-ipfire0
+VER = 4.14.44
+ARM_PATCHES = 4.14.44-ipfire0
THISAPP = linux-$(VER)
DL_FILE = linux-$(VER).tar.xz
@@ -75,8 +75,8 @@ 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 = e2ee85c1c56cc048b072ccd469862233
-arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5 = 12f346d38b519c71d9e9837529d53494
+$(DL_FILE)_MD5 = f899e4f755a6a23396115674fae81986
+arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5 = 1d66d7f85b77d06da04d8421f92e0ab9
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2018-05-27 14:09 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=20180527140919.D99841081DF2@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