From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] data/gentoo-news:master commit in: 2024-03-22-new-23-profiles/
Date: Sun, 24 Mar 2024 10:26:42 +0000 (UTC) [thread overview]
Message-ID: <1711275996.d3591106b1456128fb9f24a4d6261c101b6dbfec.sam@gentoo> (raw)
commit: d3591106b1456128fb9f24a4d6261c101b6dbfec
Author: Aliaksei Urbanski <aliaksei.urbanski <AT> gmail <DOT> com>
AuthorDate: Fri Mar 22 23:17:49 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Mar 24 10:26:36 2024 +0000
URL: https://gitweb.gentoo.org/data/gentoo-news.git/commit/?id=d3591106
2024-03-22-new-23-profiles: Fix a reference from step 10 to step 4
Signed-off-by: Aliaksei Urbanski <aliaksei.urbanski <AT> gmail.com>
Closes: https://github.com/gentoo/gentoo-news/pull/3
Signed-off-by: Sam James <sam <AT> gentoo.org>
2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt b/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt
index 0e2eeba..d8f6fd3 100644
--- a/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt
+++ b/2024-03-22-new-23-profiles/2024-03-22-new-23-profiles.en.txt
@@ -116,7 +116,7 @@ instructions with a critical eye then.
or for musl-based systems
emerge --ask --oneshot --getbinpkg sys-libs/musl
-10. Re-run "emerge --info" and check if CHOST has changed compared to step 3.
+10. Re-run "emerge --info" and check if CHOST has changed compared to step 4.
If the CHOST has NOT changed, skip to step 13 (env-update). Otherwise,
next reply other threads:[~2024-03-24 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-24 10:26 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-24 16:50 [gentoo-commits] data/gentoo-news:master commit in: 2024-03-22-new-23-profiles/ Andreas K. Hüttel
2024-03-22 19:26 Andreas K. Hüttel
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=1711275996.d3591106b1456128fb9f24a4d6261c101b6dbfec.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