public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Yixun Lan" <dlan@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-firmware/ipxe/
Date: Sun, 23 Jan 2022 08:05:59 +0000 (UTC)	[thread overview]
Message-ID: <1642925077.212f990f6c0ba5d32bb3183dbba4223535f27e4e.dlan@gentoo> (raw)

commit:     212f990f6c0ba5d32bb3183dbba4223535f27e4e
Author:     Yongxiang Liang <tanekliang <AT> gmail <DOT> com>
AuthorDate: Sun Jan  9 11:55:43 2022 +0000
Commit:     Yixun Lan <dlan <AT> gentoo <DOT> org>
CommitDate: Sun Jan 23 08:04:37 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=212f990f

sys-firmware/ipxe: keyword ~riscv

Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Yongxiang Liang <tanekliang <AT> gmail.com>
Signed-off-by: Yixun Lan <dlan <AT> gentoo.org>

 sys-firmware/ipxe/ipxe-1.21.1.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sys-firmware/ipxe/ipxe-1.21.1.ebuild b/sys-firmware/ipxe/ipxe-1.21.1.ebuild
index 32f157da7b8d..60e2c0fc830d 100644
--- a/sys-firmware/ipxe/ipxe-1.21.1.ebuild
+++ b/sys-firmware/ipxe/ipxe-1.21.1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=7
@@ -14,7 +14,7 @@ S="${WORKDIR}/${P}/src"
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~ia64 ~mips ~ppc ppc64 x86"
+KEYWORDS="~alpha amd64 ~arm arm64 ~hppa ~ia64 ~mips ~ppc ppc64 ~riscv x86"
 IUSE="+binary efi ipv6 iso lkrn +qemu undi usb vmware"
 REQUIRED_USE="!amd64? ( !x86? ( binary ) )"
 


             reply	other threads:[~2022-01-23  8:06 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-23  8:05 Yixun Lan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-06  4:16 [gentoo-commits] repo/gentoo:master commit in: sys-firmware/ipxe/ Sam James
2025-01-06  3:32 Sam James
2025-01-06  3:24 Sam James
2025-01-06  3:24 Sam James
2024-11-02 12:46 Joonas Niilola
2024-11-02 12:46 Joonas Niilola
2024-07-03 21:08 Matthias Maier
2024-01-07 17:19 Andrew Ammerlaan
2023-08-17  7:49 Andrew Ammerlaan
2023-07-15  7:39 David Seifert
2023-07-15  7:14 David Seifert
2023-06-18  3:47 Matthias Maier
2023-06-18  3:01 Matthias Maier
2022-09-24 20:52 Andreas Sturmlechner
2022-05-19 12:19 WANG Xuerui
2021-05-17  7:49 Agostino Sarubbo
2021-05-17  7:47 Agostino Sarubbo
2021-05-16 23:43 Sam James
2021-05-16  0:03 Sam James
2021-04-24 16:51 David Seifert
2021-04-24 16:51 David Seifert
2021-04-05  1:06 Matthias Maier
2020-12-18  9:00 Michał Górny
2020-11-07  3:49 Georgy Yakovlev
2020-08-19 22:40 Sam James
2019-08-19 11:37 Agostino Sarubbo
2019-08-18 21:51 Agostino Sarubbo
2019-07-28 20:20 Matthias Maier
2018-06-23 13:48 Mikle Kolyada
2018-06-17 23:29 Thomas Deutschmann
2018-06-10  3:41 Matthias Maier
2018-02-12  0:01 Matthias Maier
2018-02-12  0:01 Matthias Maier
2016-12-20 13:29 Tobias Klausmann
2016-06-23 14:30 Mike Frysinger
2016-06-21  6:24 Mike Frysinger
2016-06-21  4:33 Mike Frysinger
2016-06-21  4:33 Mike Frysinger
2016-06-21  4:33 Mike Frysinger
2016-04-19 20:05 Ian Stakenvicius
2015-08-30  1:09 Mike Frysinger
2015-08-30  1:06 Mike Frysinger

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=1642925077.212f990f6c0ba5d32bb3183dbba4223535f27e4e.dlan@gentoo \
    --to=dlan@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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