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-ruby/term-ansicolor/
Date: Sun,  6 Oct 2024 11:52:53 +0000 (UTC)	[thread overview]
Message-ID: <1728215429.77c1f404d499ddd067910a7ace30c9172548f666.sam@gentoo> (raw)

commit:     77c1f404d499ddd067910a7ace30c9172548f666
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Oct  6 11:50:29 2024 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Oct  6 11:50:29 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=77c1f404

dev-ruby/term-ansicolor: Stabilize 1.11.2 amd64, #941034

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

 dev-ruby/term-ansicolor/term-ansicolor-1.11.2.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-ruby/term-ansicolor/term-ansicolor-1.11.2.ebuild b/dev-ruby/term-ansicolor/term-ansicolor-1.11.2.ebuild
index 5af21af160e2..b8e771a0dd55 100644
--- a/dev-ruby/term-ansicolor/term-ansicolor-1.11.2.ebuild
+++ b/dev-ruby/term-ansicolor/term-ansicolor-1.11.2.ebuild
@@ -17,7 +17,7 @@ HOMEPAGE="https://github.com/flori/term-ansicolor"
 
 LICENSE="GPL-2"
 SLOT="0"
-KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ppc ppc64 ~sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
+KEYWORDS="~alpha amd64 ~arm ~arm64 ~hppa ~ppc ppc64 ~sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x64-solaris"
 
 ruby_add_rdepend ">=dev-ruby/tins-1.0"
 


             reply	other threads:[~2024-10-06 11:53 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-06 11:52 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-06 14:29 [gentoo-commits] repo/gentoo:master commit in: dev-ruby/term-ansicolor/ Arthur Zamarin
2024-10-06 11:52 Sam James
2024-10-06 11:12 Sam James
2024-08-19 17:33 Sam James
2024-08-19 17:33 Sam James
2024-08-19 17:33 Sam James
2024-08-19 10:44 Arthur Zamarin
2024-08-19 10:44 Arthur Zamarin
2024-08-19  5:46 Hans de Graaff
2024-08-19  5:46 Hans de Graaff
2024-07-11 16:19 Hans de Graaff
2024-06-20 20:39 Arthur Zamarin
2024-06-20 20:20 Arthur Zamarin
2024-06-20 16:22 Sam James
2024-06-20 10:13 Sam James
2024-06-20  8:02 Sam James
2024-06-20  5:30 Hans de Graaff
2024-04-14  6:07 Hans de Graaff
2024-03-20  6:10 Hans de Graaff
2024-03-17  6:46 Hans de Graaff
2023-04-01 23:53 Sam James
2022-06-20  4:49 Hans de Graaff
2022-04-17  6:57 Hans de Graaff
2022-04-17  6:57 Hans de Graaff
2021-07-20  5:18 Hans de Graaff
2021-01-06 18:32 Fabian Groffen
2020-07-27  2:09 Sam James
2020-04-07 18:53 Hans de Graaff
2019-05-03  4:54 Hans de Graaff
2019-05-02 21:37 Mikle Kolyada
2019-05-02 21:37 Mikle Kolyada
2019-04-28 20:34 Thomas Deutschmann
2019-04-27 16:25 Sergei Trofimovich
2019-04-27 15:48 Sergei Trofimovich
2019-04-26 20:35 Sergei Trofimovich
2019-04-20 17:46 Mikle Kolyada
2019-04-20  6:44 Hans de Graaff
2019-02-14  7:19 Sergei Trofimovich
2019-01-19  8:07 Hans de Graaff
2019-01-15  6:02 Hans de Graaff
2018-11-03  6:32 Hans de Graaff
2018-03-28  4:42 Hans de Graaff
2017-12-22  6:03 Hans de Graaff
2017-10-23 18:42 Thomas Deutschmann
2017-10-22  7:06 Hans de Graaff
2017-09-08 19:24 Markus Meier
2017-09-04  7:30 Tobias Klausmann
2017-08-25  7:03 Sergei Trofimovich
2017-08-23 21:43 Sergei Trofimovich
2017-06-29  5:19 Hans de Graaff
2017-06-28  8:08 Sergei Trofimovich
2017-06-19  5:19 Hans de Graaff
2017-04-15  6:06 Hans de Graaff
2017-03-29  5:21 Hans de Graaff
2017-03-26  7:50 Hans de Graaff
2017-03-26  7:50 Hans de Graaff
2016-12-09  6:59 Hans de Graaff
2016-09-28  5:37 Hans de Graaff
2016-07-22 19:04 Hans de Graaff
2016-06-05  7:59 Hans de Graaff
2016-04-17 14:43 Manuel Rüger
2015-11-11  6:27 Hans de Graaff
2015-10-16  7:14 Mikle Kolyada
2015-09-18  5:12 Hans de Graaff
2015-09-17 16:03 Tobias Klausmann

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=1728215429.77c1f404d499ddd067910a7ace30c9172548f666.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