From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/libsigsegv/
Date: Sat, 11 Feb 2023 05:37:44 +0000 (UTC) [thread overview]
Message-ID: <1676093851.8f4b683208209c9b71cd97faf50a2b07b3a49bc9.sam@gentoo> (raw)
commit: 8f4b683208209c9b71cd97faf50a2b07b3a49bc9
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Feb 11 05:37:31 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Feb 11 05:37:31 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=8f4b6832
dev-libs/libsigsegv: Stabilize 2.14 sparc, #893888
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-libs/libsigsegv/libsigsegv-2.14.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-libs/libsigsegv/libsigsegv-2.14.ebuild b/dev-libs/libsigsegv/libsigsegv-2.14.ebuild
index 53d807337f27..a85ce3c144f7 100644
--- a/dev-libs/libsigsegv/libsigsegv-2.14.ebuild
+++ b/dev-libs/libsigsegv/libsigsegv-2.14.ebuild
@@ -11,7 +11,7 @@ SRC_URI="mirror://gnu/libsigsegv/${P}.tar.gz"
LICENSE="GPL-2+"
SLOT="0"
-KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~mips ~ppc ppc64 ~riscv ~s390 ~sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~x86-solaris"
+KEYWORDS="~alpha amd64 arm ~arm64 ~hppa ~ia64 ~mips ~ppc ppc64 ~riscv ~s390 sparc x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~x86-solaris"
src_prepare() {
default
next reply other threads:[~2023-02-11 5:37 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-11 5:37 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-24 22:43 [gentoo-commits] repo/gentoo:master commit in: dev-libs/libsigsegv/ Sam James
2024-03-24 22:42 Sam James
2024-03-24 22:42 Sam James
2024-03-24 22:42 Sam James
2024-03-24 22:41 Sam James
2024-03-24 22:41 Sam James
2023-02-11 5:37 Sam James
2023-02-11 5:37 Sam James
2023-02-11 5:37 Sam James
2023-02-11 5:37 Sam James
2023-02-11 5:37 Sam James
2022-07-10 15:45 Sam James
2022-06-07 9:06 Sam James
2022-05-10 16:39 Jakov Smolić
2022-01-09 1:06 Sam James
2021-08-12 3:10 Yixun Lan
2021-05-30 5:15 Sam James
2021-05-28 19:39 Agostino Sarubbo
2021-05-28 19:39 Agostino Sarubbo
2021-05-28 19:11 Sam James
2021-05-28 12:05 Agostino Sarubbo
2021-05-28 12:02 Agostino Sarubbo
2021-03-18 20:18 Ulrich Müller
2021-02-03 8:23 Ulrich Müller
2021-02-03 8:23 Ulrich Müller
2018-06-26 16:04 Mikle Kolyada
2018-06-19 17:29 Tobias Klausmann
2018-06-06 16:37 Sergei Trofimovich
2018-06-02 17:51 Sergei Trofimovich
2018-05-25 4:18 Matt Turner
2018-05-25 4:18 Matt Turner
2018-05-01 14:14 José María Alonso
2018-04-28 11:37 Mikle Kolyada
2018-04-22 22:11 Matt Turner
2018-04-18 7:10 Sergei Trofimovich
2018-04-10 11:32 Tobias Klausmann
2018-04-08 14:21 Aaron Bauman
2018-03-09 19:26 José María Alonso
2018-03-08 19:35 José María Alonso
2018-01-22 18:24 Markus Meier
2017-12-16 17:24 Tobias Klausmann
2017-11-30 22:16 Sergei Trofimovich
2017-11-30 22:02 Sergei Trofimovich
2017-11-30 22:02 Sergei Trofimovich
2017-11-30 21:52 Sergei Trofimovich
2017-11-30 20:19 Tobias Klausmann
2017-07-02 17:05 Alexis Ballier
2017-05-16 21:26 José María Alonso
2017-02-25 10:09 José María Alonso
2016-06-16 12:12 José María Alonso
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=1676093851.8f4b683208209c9b71cd97faf50a2b07b3a49bc9.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