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/tornado/
Date: Fri, 22 Nov 2024 13:55:10 +0000 (UTC)	[thread overview]
Message-ID: <1732283683.46ffc1b8ac1b73f95025e55d483ac141bd9ae0c2.sam@gentoo> (raw)

commit:     46ffc1b8ac1b73f95025e55d483ac141bd9ae0c2
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Nov 22 13:54:43 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Nov 22 13:54:43 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=46ffc1b8

dev-python/tornado: Stabilize 6.4.2 ppc, #944394

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

 dev-python/tornado/tornado-6.4.2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-python/tornado/tornado-6.4.2.ebuild b/dev-python/tornado/tornado-6.4.2.ebuild
index 2964999c2fc3..4da20b713c9e 100644
--- a/dev-python/tornado/tornado-6.4.2.ebuild
+++ b/dev-python/tornado/tornado-6.4.2.ebuild
@@ -19,7 +19,7 @@ HOMEPAGE="
 
 LICENSE="Apache-2.0"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~loong ~m68k ~mips ~ppc ppc64 ~riscv ~s390 sparc ~x86 ~amd64-linux ~x86-linux ~arm64-macos ~x64-macos"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~loong ~m68k ~mips ppc ppc64 ~riscv ~s390 sparc ~x86 ~amd64-linux ~x86-linux ~arm64-macos ~x64-macos"
 IUSE="test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2024-11-22 13:55 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-22 13:55 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-22 18:24 [gentoo-commits] repo/gentoo:master commit in: dev-python/tornado/ Arthur Zamarin
2024-11-22 18:24 Arthur Zamarin
2024-11-22 15:51 Sam James
2024-11-22 13:55 Sam James
2024-11-22 13:55 Sam James
2024-11-22 12:32 Michał Górny
2024-07-01  4:35 Arthur Zamarin
2024-06-28 11:12 Michał Górny
2024-06-24  1:16 Sam James
2024-06-22 17:18 Sam James
2024-06-22 17:18 Sam James
2024-06-22 13:49 Arthur Zamarin
2024-06-22 13:48 Arthur Zamarin
2024-06-22 13:48 Arthur Zamarin
2024-06-22 13:48 Arthur Zamarin
2024-06-07  1:59 Michał Górny
2023-12-27  4:33 Michał Górny
2023-12-27  1:36 Ionen Wolkens
2023-12-15 17:19 Arthur Zamarin
2023-12-15 17:14 Arthur Zamarin
2023-12-15 17:14 Arthur Zamarin
2023-12-15 17:04 Arthur Zamarin
2023-12-15 11:20 Arthur Zamarin
2023-12-15 11:02 Arthur Zamarin
2023-09-25 18:52 Michał Górny
2023-09-25 17:06 Arthur Zamarin
2023-09-25 17:06 Arthur Zamarin
2023-09-25 17:06 Arthur Zamarin
2023-09-25 17:06 Arthur Zamarin
2023-09-25 17:06 Arthur Zamarin
2023-09-25 17:05 Arthur Zamarin
2023-09-25 16:54 Arthur Zamarin
2023-09-25 16:54 Arthur Zamarin
2023-08-20 16:19 Benda XU
2023-08-12  2:19 Michał Górny
2023-08-11 18:42 Arthur Zamarin
2023-08-11 18:42 Arthur Zamarin
2023-08-04 21:38 Sam James
2023-07-09 18:24 Arthur Zamarin
2023-07-09 17:19 Arthur Zamarin
2023-07-09 17:10 Arthur Zamarin
2023-07-09 16:55 Arthur Zamarin
2023-07-09 16:52 Arthur Zamarin
2023-07-09 16:52 Arthur Zamarin
2023-06-03 15:08 Arthur Zamarin
2023-06-03 15:05 Arthur Zamarin
2023-05-29  9:31 Michał Górny
2023-05-29  7:55 Michał Górny
2023-05-29  0:41 Sam James
2023-05-16 19:29 Jakov Smolić
2023-05-16 18:03 Arthur Zamarin
2023-05-16 17:07 Sam James
2023-05-16  7:58 Sam James
2023-05-16  6:28 Sam James
2023-05-16  6:28 Sam James
2023-05-16  6:28 Sam James
2023-05-16  5:19 Michał Górny
2023-04-29 17:52 Michał Górny
2023-04-22  6:17 Michał Górny
2023-04-19  6:34 Michał Górny
2023-04-19  1:07 Sam James
2023-04-12  0:38 Jakov Smolić
2023-04-11 20:11 Arthur Zamarin
2023-04-11 19:04 Sam James
2023-04-11 18:36 Arthur Zamarin
2023-04-11 18:20 Arthur Zamarin
2023-04-11 18:16 Arthur Zamarin
2023-04-11 18:16 Arthur Zamarin
2023-03-11  5:53 Michał Górny
2023-03-11  5:53 Michał Górny
2023-03-11  5:53 Michał Górny

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=1732283683.46ffc1b8ac1b73f95025e55d483ac141bd9ae0c2.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