public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-python/mkdocs-minify-plugin/
Date: Fri, 14 Apr 2023 19:43:03 +0000 (UTC)	[thread overview]
Message-ID: <1681501034.cf1d87eb4d93f473a48cbb900a810a2f2662d935.sam@gentoo> (raw)

commit:     cf1d87eb4d93f473a48cbb900a810a2f2662d935
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Apr 14 19:37:14 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Apr 14 19:37:14 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cf1d87eb

dev-python/mkdocs-minify-plugin: Keyword 0.6.4 ppc64, #888513

Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-python/mkdocs-minify-plugin/mkdocs-minify-plugin-0.6.4.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/mkdocs-minify-plugin/mkdocs-minify-plugin-0.6.4.ebuild b/dev-python/mkdocs-minify-plugin/mkdocs-minify-plugin-0.6.4.ebuild
index 5c684ebe383e..201f3111160d 100644
--- a/dev-python/mkdocs-minify-plugin/mkdocs-minify-plugin-0.6.4.ebuild
+++ b/dev-python/mkdocs-minify-plugin/mkdocs-minify-plugin-0.6.4.ebuild
@@ -20,7 +20,7 @@ SRC_URI="
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~riscv ~x86"
+KEYWORDS="~amd64 ~arm ~arm64 ~ppc ~ppc64 ~riscv ~x86"
 
 RDEPEND="
 	>=dev-python/csscompressor-0.9.5[${PYTHON_USEDEP}]


             reply	other threads:[~2023-04-14 19:43 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 19:43 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-25 11:05 [gentoo-commits] repo/gentoo:master commit in: dev-python/mkdocs-minify-plugin/ Michał Górny
2024-07-06 17:58 Michał Górny
2024-04-03  8:58 Michał Górny
2024-02-17 22:26 Sam James
2024-02-01 10:20 Andrew Ammerlaan
2023-12-30 14:32 Michał Górny
2023-12-30 14:05 Arthur Zamarin
2023-12-15  8:17 Michał Górny
2023-12-04 13:46 Michał Górny
2023-12-02  9:54 Michał Górny
2023-12-02  9:50 Michał Górny
2023-11-29 10:47 Andrew Ammerlaan
2023-09-14  9:58 Andrew Ammerlaan
2023-08-18 13:41 Andrew Ammerlaan
2023-07-26  6:03 Michał Górny
2023-04-16 18:56 Michał Górny
2023-04-16 17:15 Arthur Zamarin
2023-04-14  4:04 Sam James
2023-03-15 18:34 Arthur Zamarin
2023-03-15  7:31 Michał Górny
2023-03-15  6:52 Michał Górny
2023-02-25  5:47 Arthur Zamarin
2022-12-31 12:37 Michał Górny
2022-12-31 12:11 Sam James
2022-11-30  2:55 Michał Górny
2022-11-29 22:22 Jakov Smolić
2022-11-29  8:48 Michał Górny
2022-11-29  6:59 Michał Górny
2022-10-25 20:30 Arthur Zamarin
2022-10-22  7:46 Arthur Zamarin
2022-06-25 11:18 Michał Górny
2022-06-25  8:42 Arthur Zamarin
2022-05-24 13:02 Andrew Ammerlaan
2021-12-26  0:23 Sam James
2021-12-25 19:09 Jakov Smolić
2021-11-30 11:36 Arthur Zamarin
2021-11-25  2:54 Yixun Lan
2021-11-24 22:25 Andrew Ammerlaan
2021-11-21 19:14 Michał Górny
2021-11-21 18:39 Jakov Smolić
2021-10-20 12:17 Andrew Ammerlaan
2021-09-23 15:35 Marek Szuba
2021-09-09 15:51 Arthur Zamarin
2021-07-15  7:38 Agostino Sarubbo
2021-07-08 11:08 Andrew Ammerlaan
2021-04-13 11:07 Joonas Niilola
2021-03-11  7:18 Joonas Niilola
2020-12-08  5:53 Joonas Niilola

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=1681501034.cf1d87eb4d93f473a48cbb900a810a2f2662d935.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