public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Arthur Zamarin" <arthurzam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-lang/rust-common/
Date: Sat, 18 Jan 2025 07:12:53 +0000 (UTC)	[thread overview]
Message-ID: <1737184349.93d8984fc566fc7285eca62f0f2c53b5ecfed3b4.arthurzam@gentoo> (raw)

commit:     93d8984fc566fc7285eca62f0f2c53b5ecfed3b4
Author:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
AuthorDate: Sat Jan 18 07:12:29 2025 +0000
Commit:     Arthur Zamarin <arthurzam <AT> gentoo <DOT> org>
CommitDate: Sat Jan 18 07:12:29 2025 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=93d8984f

dev-lang/rust-common: Stabilize 1.83.0 ppc, #948228

Signed-off-by: Arthur Zamarin <arthurzam <AT> gentoo.org>

 dev-lang/rust-common/rust-common-1.83.0.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-lang/rust-common/rust-common-1.83.0.ebuild b/dev-lang/rust-common/rust-common-1.83.0.ebuild
index 7cd56daa1ad7..5c676ac678bf 100644
--- a/dev-lang/rust-common/rust-common-1.83.0.ebuild
+++ b/dev-lang/rust-common/rust-common-1.83.0.ebuild
@@ -27,7 +27,7 @@ S="${WORKDIR}/${MY_P}-src"
 
 LICENSE="|| ( MIT Apache-2.0 ) BSD BSD-1 BSD-2 BSD-4"
 SLOT="0"
-KEYWORDS="amd64 arm arm64 ~loong ~mips ~ppc ppc64 ~riscv sparc x86"
+KEYWORDS="amd64 arm arm64 ~loong ~mips ppc ppc64 ~riscv sparc x86"
 
 # Legacy non-slotted versions bash completions will collide.
 RDEPEND="


             reply	other threads:[~2025-01-18  7:12 UTC|newest]

Thread overview: 73+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-18  7:12 Arthur Zamarin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-20 12:48 [gentoo-commits] repo/gentoo:master commit in: dev-lang/rust-common/ Arthur Zamarin
2025-09-20 12:48 Arthur Zamarin
2025-09-19 19:10 Sam James
2025-09-19 18:38 Sam James
2025-09-19  9:35 Arthur Zamarin
2025-09-19  9:35 Arthur Zamarin
2025-09-19  6:19 Arthur Zamarin
2025-09-19  6:04 Arthur Zamarin
2025-08-08  8:39 Arthur Zamarin
2025-08-04 15:17 Sam James
2025-08-04 15:17 Sam James
2025-08-04 15:17 Sam James
2025-08-04 15:17 Sam James
2025-07-29  8:36 Matt Jolly
2025-06-27 10:42 Arthur Zamarin
2025-06-16  2:57 Sam James
2025-06-16  2:32 Sam James
2025-06-16  2:32 Sam James
2025-06-15 18:07 Arthur Zamarin
2025-06-15 16:12 Sam James
2025-06-15 15:22 Sam James
2025-06-15 15:22 Sam James
2025-06-15 14:45 Sam James
2025-06-15 14:45 Sam James
2025-06-15 14:45 Sam James
2025-06-15 14:42 Sam James
2025-06-05 22:39 Sam James
2025-06-05  2:52 Sam James
2025-06-03 21:38 Matt Jolly
2025-06-03 20:05 Sam James
2025-06-03 20:05 Sam James
2025-05-16  6:01 Arthur Zamarin
2025-05-06  2:20 Matt Jolly
2025-04-23 15:18 Sam James
2025-04-23 11:37 Matt Jolly
2025-04-21 16:55 Arthur Zamarin
2025-04-21 16:15 Arthur Zamarin
2025-04-21  7:43 Sam James
2025-04-19 22:19 Sam James
2025-04-19 20:29 Sam James
2025-04-03 19:03 Arthur Zamarin
2025-04-01 23:38 Matt Jolly
2025-03-19 20:59 Arthur Zamarin
2025-02-28  7:10 Arthur Zamarin
2025-02-22  8:18 Arthur Zamarin
2025-02-22  8:17 Arthur Zamarin
2025-02-22  8:17 Arthur Zamarin
2025-02-21 19:54 Arthur Zamarin
2025-02-21 19:54 Arthur Zamarin
2025-02-21 18:50 Arthur Zamarin
2025-02-21 17:36 Arthur Zamarin
2025-02-21 11:14 Arthur Zamarin
2025-02-21 11:14 Arthur Zamarin
2025-02-05 18:37 Arthur Zamarin
2025-01-18  7:12 Arthur Zamarin
2025-01-17 17:08 Arthur Zamarin
2025-01-17 16:00 Arthur Zamarin
2025-01-17 16:00 Arthur Zamarin
2025-01-17 16:00 Arthur Zamarin
2025-01-17 16:00 Arthur Zamarin
2025-01-11  8:10 Arthur Zamarin
2025-01-04 20:28 Sam James
2025-01-04 20:28 Sam James
2025-01-04 16:22 Arthur Zamarin
2025-01-04 16:17 Sam James
2025-01-04 14:37 Sam James
2025-01-04 14:27 Sam James
2025-01-04 14:13 Sam James
2024-12-01  8:23 Arthur Zamarin
2024-11-10 13:03 Sam James
2024-11-09  7:42 Sam James
2024-11-09  6:42 Sam James

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=1737184349.93d8984fc566fc7285eca62f0f2c53b5ecfed3b4.arthurzam@gentoo \
    --to=arthurzam@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