From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: [PR PATCH] intel-ucode: update to 20190918
Date: Fri, 20 Sep 2019 18:01:07 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14607@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 312 bytes --]
There is a new pull request by k4leg against master on the void-packages repository
https://github.com/k4leg/void-packages patch-2
https://github.com/void-linux/void-packages/pull/14607
intel-ucode: update to 20190918
A patch file from https://github.com/void-linux/void-packages/pull/14607.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-patch-2-14607.patch --]
[-- Type: text/x-diff, Size: 700 bytes --]
From 089fc1447035055505d5cb8887c73a73793e5b8f Mon Sep 17 00:00:00 2001
From: k4leg <39882583+k4leg@users.noreply.github.com>
Date: Fri, 20 Sep 2019 19:00:49 +0300
Subject: [PATCH] intel-ucode: update to 20190918
---
srcpkgs/intel-ucode/template | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/srcpkgs/intel-ucode/template b/srcpkgs/intel-ucode/template
index 109edac179b..f40476177c6 100644
--- a/srcpkgs/intel-ucode/template
+++ b/srcpkgs/intel-ucode/template
@@ -1,6 +1,6 @@
# Template file for 'intel-ucode'
pkgname=intel-ucode
-version=20190618
+version=20190918
revision=1
archs="i686* x86_64*"
wrksrc="Intel-Linux-Processor-Microcode-Data-Files-microcode-${version}"
next reply other threads:[~2019-09-20 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-20 16:01 voidlinux-github [this message]
2019-09-20 16:09 ` [PR PATCH] [Updated] " voidlinux-github
2019-09-20 16:09 ` voidlinux-github
2019-09-20 21:51 ` voidlinux-github
2019-09-21 12:12 ` [PR PATCH] [Closed]: " voidlinux-github
-- strict thread matches above, loose matches on Subject: below --
2019-09-20 15:27 [PR PATCH] " voidlinux-github
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-14607@inbox.vuxu.org \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).