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-libs/libyaml/
Date: Thu, 21 Jan 2021 22:31:55 +0000 (UTC)	[thread overview]
Message-ID: <1611268299.640505016870846a2dca108c3bdf7488f86769e9.sam@gentoo> (raw)

commit:     640505016870846a2dca108c3bdf7488f86769e9
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Thu Jan 21 22:31:39 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Thu Jan 21 22:31:39 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=64050501

dev-libs/libyaml: Stabilize 0.2.5 sparc, #764893

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

 dev-libs/libyaml/libyaml-0.2.5.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-libs/libyaml/libyaml-0.2.5.ebuild b/dev-libs/libyaml/libyaml-0.2.5.ebuild
index ba73c56e196..89e8378ce0b 100644
--- a/dev-libs/libyaml/libyaml-0.2.5.ebuild
+++ b/dev-libs/libyaml/libyaml-0.2.5.ebuild
@@ -11,7 +11,7 @@ SRC_URI="https://github.com/yaml/${PN}/archive/${PV}.tar.gz -> ${P}.tar.gz"
 
 LICENSE="MIT"
 SLOT="0"
-KEYWORDS="~alpha amd64 ~arm arm64 hppa ~ia64 ~m68k ~mips ppc ~ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 ~arm arm64 hppa ~ia64 ~m68k ~mips ppc ~ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
 IUSE="doc static-libs test"
 RESTRICT="!test? ( test )"
 


             reply	other threads:[~2021-01-21 22:32 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 22:31 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-30 13:55 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libyaml/ Fabian Groffen
2022-07-29  4:17 Sam James
2021-03-21 19:00 David Seifert
2021-02-05 21:37 Sam James
2021-01-24 23:21 Sam James
2021-01-24 13:33 Sam James
2021-01-20 17:02 Sergei Trofimovich
2021-01-20  9:30 Sam James
2021-01-20  9:29 Sam James
2021-01-20  9:28 Sam James
2021-01-20  0:05 Sam James
2020-12-27 19:16 Fabian Groffen
2020-12-27 14:21 Fabian Groffen
2020-06-02  0:25 Patrick McLean
2019-11-19  1:28 Patrick McLean
2019-11-17  5:08 Tim Harder
2019-09-01 18:30 Mikle Kolyada
2019-09-01 18:30 Mikle Kolyada
2019-09-01 18:30 Mikle Kolyada
2019-08-23 10:04 Agostino Sarubbo
2019-08-23 10:00 Agostino Sarubbo
2019-08-18 21:51 Agostino Sarubbo
2019-08-17 20:41 Sergei Trofimovich
2019-08-17 20:33 Sergei Trofimovich
2019-08-17 20:22 Sergei Trofimovich
2019-08-17 20:17 Sergei Trofimovich
2019-08-16 22:38 Thomas Deutschmann
2019-08-16 22:16 Aaron Bauman
2019-08-15 18:51 Sergei Trofimovich
2019-05-11  5:51 Tim Harder
2019-05-05 12:46 Mikle Kolyada
2019-04-03  4:46 Tim Harder
2018-06-30 17:34 Tim Harder
2017-02-24  4:39 Mike Frysinger
2017-01-21  9:56 Tim Harder
2017-01-07  9:44 Jeroen Roovers
2016-11-29 17:31 Markus Meier
2016-11-25 18:54 Agostino Sarubbo
2016-11-25 18:27 Agostino Sarubbo
2016-11-23 17:59 Tobias Klausmann
2016-08-30  1:51 Tim Harder

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=1611268299.640505016870846a2dca108c3bdf7488f86769e9.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