public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-apps/lshw/
Date: Fri, 12 May 2023 16:26:45 +0000 (UTC)	[thread overview]
Message-ID: <1683908792.cff4f034721ef3faf9cc98c17d6d467c3341296f.sam@gentoo> (raw)

commit:     cff4f034721ef3faf9cc98c17d6d467c3341296f
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri May 12 16:26:32 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri May 12 16:26:32 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cff4f034

sys-apps/lshw: Stabilize 02.19.2b_p20220831 sparc, #906205

Signed-off-by: Sam James <sam <AT> gentoo.org>

 sys-apps/lshw/lshw-02.19.2b_p20220831.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/sys-apps/lshw/lshw-02.19.2b_p20220831.ebuild b/sys-apps/lshw/lshw-02.19.2b_p20220831.ebuild
index f190fc882373..6af06ab03385 100644
--- a/sys-apps/lshw/lshw-02.19.2b_p20220831.ebuild
+++ b/sys-apps/lshw/lshw-02.19.2b_p20220831.ebuild
@@ -16,7 +16,7 @@ SRC_URI="https://ezix.org/src/pkg/lshw/archive/${MY_COMMIT}.tar.gz -> ${P}-${MY_
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~ppc ~ppc64 ~riscv ~sparc ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~ppc ~ppc64 ~riscv sparc ~x86 ~amd64-linux ~x86-linux"
 IUSE="gtk sqlite static"
 
 REQUIRED_USE="static? ( !gtk !sqlite )"


             reply	other threads:[~2023-05-12 16:26 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-12 16:26 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-25 17:31 [gentoo-commits] repo/gentoo:master commit in: sys-apps/lshw/ Arthur Zamarin
2024-05-23 21:57 Sam James
2024-05-23 21:56 Sam James
2024-05-23 15:56 Arthur Zamarin
2024-05-23 15:56 Arthur Zamarin
2024-05-23 15:56 Arthur Zamarin
2024-05-23 15:56 Arthur Zamarin
2024-03-29 15:38 Ben Kohler
2024-02-28 16:25 Ben Kohler
2024-02-28 16:07 Ben Kohler
2024-01-22  8:36 Sam James
2023-11-03 12:23 Ben Kohler
2023-09-02  0:23 Ben Kohler
2023-05-12 16:31 Sam James
2023-05-12 16:31 Sam James
2023-05-12 16:31 Sam James
2023-05-12 16:31 Sam James
2023-05-12 16:26 Sam James
2023-05-12 16:26 Sam James
2023-03-01 15:08 Ben Kohler
2022-02-19 13:14 Ben Kohler
2022-02-06 12:59 Ben Kohler
2022-01-18 22:16 Sam James
2022-01-14 15:23 Arthur Zamarin
2022-01-14 13:46 Jakov Smolić
2022-01-14 13:46 Jakov Smolić
2022-01-14 13:22 Arthur Zamarin
2022-01-14 13:22 Arthur Zamarin
2022-01-14 13:22 Arthur Zamarin
2021-12-25  0:02 Mike Gilbert
2021-12-07 20:29 Sam James
2021-11-28 20:08 Mike Gilbert
2021-08-10  0:02 Marek Szuba
2021-07-13 13:44 Ben Kohler
2021-07-04 14:03 Ulrich Müller
2021-05-29 15:33 Sam James
2021-05-28 12:04 Agostino Sarubbo
2021-05-28 12:03 Agostino Sarubbo
2021-05-27 19:18 Sam James
2021-05-27 19:14 Sam James
2021-05-18 15:18 Ben Kohler
2021-05-17  8:53 Agostino Sarubbo
2021-05-17  7:49 Agostino Sarubbo
2021-05-17  3:19 Sam James
2021-05-17  3:04 Sam James
2021-05-17  2:37 Sam James
2021-05-16 23:41 Sam James
2021-05-16 23:41 Sam James
2021-04-27  8:07 David Seifert
2021-04-26 17:48 Ben Kohler
2021-04-21 14:13 Guilherme Amadio
2021-04-03 15:44 Sam James
2021-03-23 15:22 Ben Kohler
2021-03-23 15:22 Ben Kohler
2021-03-23 15:22 Ben Kohler
2020-08-19 20:06 Sam James
2020-06-06 19:31 Mart Raudsepp
2017-11-06 21:20 Sergei Trofimovich
2017-09-30 23:44 Thomas Deutschmann
2017-09-26 22:37 Manuel Rüger
2017-09-22 19:40 Sergei Trofimovich
2017-09-09 18:45 Sergei Trofimovich
2017-09-09 10:27 Markus Meier
2017-09-04  7:30 Tobias Klausmann
2017-09-01 22:36 Sergei Trofimovich
2017-09-01  2:22 Tim Harder
2017-03-15  6:02 Mike Frysinger
2017-03-15  5:42 Mike Frysinger
2016-05-20 15:45 Mike Frysinger
2016-05-20 15:41 Mike Frysinger
2016-05-15 20:40 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=1683908792.cff4f034721ef3faf9cc98c17d6d467c3341296f.sam@gentoo \
    --to=sam@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