From: Arne Fitzenreiter <git@ipfire.org>
To: ipfire-scm@lists.ipfire.org
Subject: [git.ipfire.org] IPFire 2.x development tree branch, next, updated. 4d43b3dcb1b31444ff49f3cc0ea4b04d4e6599fb
Date: Fri, 12 Jun 2020 15:48:18 +0000 [thread overview]
Message-ID: <49k4rL61dcz2xld@people01.haj.ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 3409 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 4d43b3dcb1b31444ff49f3cc0ea4b04d4e6599fb (commit)
from f3a59d63e27648c56da7296f48fe7382d8daedad (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 4d43b3dcb1b31444ff49f3cc0ea4b04d4e6599fb
Author: Arne Fitzenreiter <arne_f(a)ipfire.org>
Date: Fri Jun 12 17:47:29 2020 +0200
intel-microcode: update to 20200609
Signed-off-by: Arne Fitzenreiter <arne_f(a)ipfire.org>
-----------------------------------------------------------------------
Summary of changes:
.../{oldcore/121 => core/146}/filelists/i586/intel-microcode | 0
.../{oldcore/121 => core/146}/filelists/x86_64/intel-microcode | 0
lfs/intel-microcode | 6 +++---
3 files changed, 3 insertions(+), 3 deletions(-)
copy config/rootfiles/{oldcore/121 => core/146}/filelists/i586/intel-microcode (100%)
copy config/rootfiles/{oldcore/121 => core/146}/filelists/x86_64/intel-microcode (100%)
Difference in files:
diff --git a/config/rootfiles/core/146/filelists/i586/intel-microcode b/config/rootfiles/core/146/filelists/i586/intel-microcode
new file mode 120000
index 000000000..f03e84778
--- /dev/null
+++ b/config/rootfiles/core/146/filelists/i586/intel-microcode
@@ -0,0 +1 @@
+../../../../common/i586/intel-microcode
\ No newline at end of file
diff --git a/config/rootfiles/core/146/filelists/x86_64/intel-microcode b/config/rootfiles/core/146/filelists/x86_64/intel-microcode
new file mode 120000
index 000000000..d5ac074e2
--- /dev/null
+++ b/config/rootfiles/core/146/filelists/x86_64/intel-microcode
@@ -0,0 +1 @@
+../../../../common/x86_64/intel-microcode
\ No newline at end of file
diff --git a/lfs/intel-microcode b/lfs/intel-microcode
index 0b60a0c77..494062784 100644
--- a/lfs/intel-microcode
+++ b/lfs/intel-microcode
@@ -1,7 +1,7 @@
###############################################################################
# #
# IPFire.org - A linux based firewall #
-# Copyright (C) 2007-2019 IPFire Team <info(a)ipfire.org> #
+# Copyright (C) 2007-2020 IPFire Team <info(a)ipfire.org> #
# #
# This program is free software: you can redistribute it and/or modify #
# it under the terms of the GNU General Public License as published by #
@@ -24,7 +24,7 @@
include Config
-VER = 20191115
+VER = 20200609
THISAPP = Intel-Linux-Processor-Microcode-Data-Files-microcode-$(VER)
DL_FILE = $(THISAPP).tar.gz
@@ -41,7 +41,7 @@ objects = $(DL_FILE)
$(DL_FILE) = $(DL_FROM)/$(DL_FILE)
-$(DL_FILE)_MD5 = 49cc3595934772b54b6218f8dbe64a94
+$(DL_FILE)_MD5 = a03e827c5c43be594f7f34d75b1706f9
install : $(TARGET)
hooks/post-receive
--
IPFire 2.x development tree
reply other threads:[~2020-06-12 15:48 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=49k4rL61dcz2xld@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