From: "Georgy Yakovlev" <gyakovlev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/releng:master commit in: tools/, releases/specs/ppc/ppc64le/
Date: Mon, 12 Dec 2022 18:36:17 +0000 (UTC) [thread overview]
Message-ID: <1670870159.b30225aff60939ff28461da185f749a923807864.gyakovlev@gentoo> (raw)
commit: b30225aff60939ff28461da185f749a923807864
Author: Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
AuthorDate: Mon Dec 12 18:35:53 2022 +0000
Commit: Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
CommitDate: Mon Dec 12 18:35:59 2022 +0000
URL: https://gitweb.gentoo.org/proj/releng.git/commit/?id=b30225af
specs/ppc64le: rename files to -mu- for consistency
Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>
...ystemd-mergedusr-power9le.spec => stage1-systemd-mu-power9le.spec} | 0
...ystemd-mergedusr-power9le.spec => stage3-systemd-mu-power9le.spec} | 0
tools/catalyst-auto-ppc64le.conf | 4 ++--
3 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/releases/specs/ppc/ppc64le/stage1-systemd-mergedusr-power9le.spec b/releases/specs/ppc/ppc64le/stage1-systemd-mu-power9le.spec
similarity index 100%
rename from releases/specs/ppc/ppc64le/stage1-systemd-mergedusr-power9le.spec
rename to releases/specs/ppc/ppc64le/stage1-systemd-mu-power9le.spec
diff --git a/releases/specs/ppc/ppc64le/stage3-systemd-mergedusr-power9le.spec b/releases/specs/ppc/ppc64le/stage3-systemd-mu-power9le.spec
similarity index 100%
rename from releases/specs/ppc/ppc64le/stage3-systemd-mergedusr-power9le.spec
rename to releases/specs/ppc/ppc64le/stage3-systemd-mu-power9le.spec
diff --git a/tools/catalyst-auto-ppc64le.conf b/tools/catalyst-auto-ppc64le.conf
index b8999b35..516f969a 100644
--- a/tools/catalyst-auto-ppc64le.conf
+++ b/tools/catalyst-auto-ppc64le.conf
@@ -11,7 +11,7 @@ OPTIONAL_SPECS+=" stage1-systemd.spec stage3-systemd.spec"
OPTIONAL_SPECS+=" stage1-systemd-mu.spec stage3-systemd-mu.spec"
OPTIONAL_SPECS+=" stage1-openrc-power9le.spec stage3-openrc-power9le.spec"
OPTIONAL_SPECS+=" stage1-systemd-power9le.spec stage3-systemd-power9le.spec"
-OPTIONAL_SPECS+=" stage1-systemd-mergedusr-power9le.spec stage3-systemd-mergedusr-power9le.spec"
+OPTIONAL_SPECS+=" stage1-systemd-mu-power9le.spec stage3-systemd-mu-power9le.spec"
OPTIONAL_SPECS+=" stage1-musl-hardened-openrc.spec stage3-musl-hardened-openrc.spec"
OPTIONAL_SPECS+=" stage1-musl-hardened-openrc-power9le.spec stage3-musl-hardened-openrc-power9le.spec"
@@ -62,7 +62,7 @@ post_build() {
stage3-systemd-power9le.spec)
upload power9le/stage3-power9le-systemd-${TIMESTAMP}*.xz*
;;
- stage3-systemd-mergedusr-power9le.spec)
+ stage3-systemd-mu-power9le.spec)
upload power9le-mergedusr/stage3-power9le-systemd-mergedusr-${TIMESTAMP}*.xz*
;;
stage3-musl-hardened-openrc.spec)
next reply other threads:[~2022-12-12 18:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 18:36 Georgy Yakovlev [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-04-05 18:53 [gentoo-commits] proj/releng:master commit in: tools/, releases/specs/ppc/ppc64le/ Andreas K. Hüttel
2023-12-25 17:06 Andreas K. Hüttel
2022-12-12 18:49 Georgy Yakovlev
2021-07-14 19:50 Georgy Yakovlev
2021-07-14 10:31 Georgy Yakovlev
2020-10-15 0:23 Matt Turner
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=1670870159.b30225aff60939ff28461da185f749a923807864.gyakovlev@gentoo \
--to=gyakovlev@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