From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-portage/prefix-toolkit/
Date: Mon, 24 Apr 2023 20:15:23 +0000 (UTC) [thread overview]
Message-ID: <1682367280.8cc8bd4b8a190493615d9f37e5869d643f327e14.sam@gentoo> (raw)
commit: 8cc8bd4b8a190493615d9f37e5869d643f327e14
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Apr 24 20:14:40 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Apr 24 20:14:40 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8cc8bd4b
app-portage/prefix-toolkit: fix comment typo
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-portage/prefix-toolkit/prefix-toolkit-8.ebuild | 2 +-
app-portage/prefix-toolkit/prefix-toolkit-9.ebuild | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/app-portage/prefix-toolkit/prefix-toolkit-8.ebuild b/app-portage/prefix-toolkit/prefix-toolkit-8.ebuild
index e48c3d2bcf18..78754f6175d0 100644
--- a/app-portage/prefix-toolkit/prefix-toolkit-8.ebuild
+++ b/app-portage/prefix-toolkit/prefix-toolkit-8.ebuild
@@ -23,7 +23,7 @@ BDEPEND="${DEPEND}
# In prefix-stack, these dependencies actually are the @system set,
# as we rely on the base prefix anyway for package management,
# which should have a proper @system set.
-# See als: pkg_preinst
+# See also: pkg_preinst
RDEPEND="${DEPEND}
prefix-stack? (
>=sys-apps/baselayout-prefix-2.6
diff --git a/app-portage/prefix-toolkit/prefix-toolkit-9.ebuild b/app-portage/prefix-toolkit/prefix-toolkit-9.ebuild
index 84d62c1b4741..f95a8588bbd6 100644
--- a/app-portage/prefix-toolkit/prefix-toolkit-9.ebuild
+++ b/app-portage/prefix-toolkit/prefix-toolkit-9.ebuild
@@ -27,7 +27,7 @@ BDEPEND="${DEPEND}
# (and pthreads4w for Winnt), but it is easier for now to install
# elt-patches, gentoo-functions and gnuconfig as well, instead of
# fixing all uses that expect them in EPREFIX rather than BROOT.
-# See als: pkg_preinst
+# See also: pkg_preinst
RDEPEND="${DEPEND}
prefix-stack? (
>=sys-apps/baselayout-prefix-2.6
next reply other threads:[~2023-04-24 20:15 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 20:15 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-13 20:03 [gentoo-commits] repo/gentoo:master commit in: app-portage/prefix-toolkit/ Fabian Groffen
2023-05-27 10:44 Fabian Groffen
2023-05-27 10:15 Fabian Groffen
2023-05-27 9:29 Sam James
2023-05-26 6:25 Sam James
2023-05-26 6:23 Sam James
2023-05-26 6:23 Sam James
2023-05-26 6:23 Sam James
2023-04-24 20:15 Sam James
2023-04-24 20:13 Sam James
2022-07-11 20:19 Jakov Smolić
2021-06-02 19:01 Sam James
2021-01-06 13:23 Fabian Groffen
2020-12-27 14:01 Fabian Groffen
2020-03-13 14:35 Michael Haubenwallner
2020-03-13 14:35 Michael Haubenwallner
2020-03-09 14:56 Michael Haubenwallner
2020-03-09 14:56 Michael Haubenwallner
2020-03-09 14:56 Michael Haubenwallner
2019-09-05 10:30 Michael Haubenwallner
2019-09-04 10:31 Michael Haubenwallner
2019-09-04 10:31 Michael Haubenwallner
2019-06-25 9:21 Michael Haubenwallner
2019-06-17 9:44 Michael Haubenwallner
2019-06-12 15:32 Michael Haubenwallner
2019-06-05 15:39 Michael Haubenwallner
2019-05-21 8:48 Michael Haubenwallner
2019-03-26 16:11 Michael Haubenwallner
2019-03-26 15:58 Michael Haubenwallner
2019-03-25 14:19 Michael Haubenwallner
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=1682367280.8cc8bd4b8a190493615d9f37e5869d643f327e14.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