From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/crossdev:master commit in: .github/workflows/
Date: Sat, 04 Jan 2025 15:19:59 +0000 (UTC) [thread overview]
Message-ID: <1735948613.6c2bf7f6c5729a8cd476f34286ec02ff4ce7e54f.sam@gentoo> (raw)
commit: 6c2bf7f6c5729a8cd476f34286ec02ff4ce7e54f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 3 23:51:54 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Jan 3 23:56:53 2025 +0000
URL: https://gitweb.gentoo.org/proj/crossdev.git/commit/?id=6c2bf7f6
ci: adjust s390x tuple name
unknown -> ibm to match profiles/
Signed-off-by: Sam James <sam <AT> gentoo.org>
.github/workflows/crossdev.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.github/workflows/crossdev.yml b/.github/workflows/crossdev.yml
index 2ba0f5f..c303d49 100644
--- a/.github/workflows/crossdev.yml
+++ b/.github/workflows/crossdev.yml
@@ -71,7 +71,7 @@ jobs:
# - target: sparc-unknown-linux-gnu
- target: sparc64-unknown-linux-gnu
- target: s390-ibm-linux-gnu
- - target: s390x-unknown-linux-gnu
+ - target: s390x-ibm-linux-gnu
# musl ebuilds don't support s390x. The target is supported upstream,
# we need to fix and test our ebuilds.
# - target: s390x-unknown-linux-musl
next reply other threads:[~2025-01-04 15:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 15:19 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-04 15:19 [gentoo-commits] proj/crossdev:master commit in: .github/workflows/ Sam James
2025-01-04 15:19 Sam James
2025-01-04 15:19 Sam James
2025-01-04 15:19 Sam James
2025-01-04 15:19 Sam James
2025-01-04 15:19 Sam James
2025-01-03 11:15 Sam James
2025-01-03 11:15 Sam James
2025-01-03 11:15 Sam James
2025-01-03 11:15 Sam James
2025-01-03 11:15 Sam James
2025-01-03 11:15 Sam James
2025-01-03 11:15 Sam James
2025-01-03 11:15 Sam James
2024-11-12 15:24 Sam James
2024-11-12 8:46 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=1735948613.6c2bf7f6c5729a8cd476f34286ec02ff4ce7e54f.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