From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 1c8e09379de62867a96ff0406f7a75841623efb8
Date: Tue, 10 Mar 2020 11:33:39 +0000 [thread overview]
Message-ID: <48cCdv6jygz2y1j@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2263 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 1c8e09379de62867a96ff0406f7a75841623efb8 (commit)
from 57fda8c8adc66acf92c24d33ccf37636e0e165bc (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 1c8e09379de62867a96ff0406f7a75841623efb8
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Tue Mar 10 07:32:48 2020 +0000
Revert "kernel: update to 4.14.172"
This reverts commit 1773544d025591d4096ee91bcc598dac19fa0f24.
with 4.14.172 klogd is not updated and the firewall log/graphs are not
working
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
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 7f44702d0..9db2efb35 100644
--- a/lfs/linux
+++ b/lfs/linux
@@ -24,8 +24,8 @@
include Config
-VER = 4.14.172
-ARM_PATCHES = 4.14.172-ipfire0
+VER = 4.14.171
+ARM_PATCHES = 4.14.171-ipfire0
THISAPP = linux-$(VER)
DL_FILE = linux-$(VER).tar.xz
@@ -34,7 +34,7 @@ DIR_APP = $(DIR_SRC)/$(THISAPP)
CFLAGS =
CXXFLAGS =
-PAK_VER = 92
+PAK_VER = 93
DEPS = ""
HEADERS_ARCH = $(BUILD_PLATFORM)
@@ -82,8 +82,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 = 782746859c7f365aeba49c08705c4c30
-arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5 = 3072dd813363b20361f80ecc748a1084
+$(DL_FILE)_MD5 = b9b2c64eb3ae7fa6023d2b8c981b5ac4
+arm-multi-patches-$(ARM_PATCHES).patch.xz_MD5 = f1d5d1dcb1d60c6f8476938070a65112
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-03-10 11:33 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=48cCdv6jygz2y1j@people01.haj.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