From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-i18n/poedit/
Date: Fri, 21 Jun 2024 18:22:49 +0000 (UTC) [thread overview]
Message-ID: <1718994146.f6c02e98fa914521af64f810557700cccf63a9de.sam@gentoo> (raw)
commit: f6c02e98fa914521af64f810557700cccf63a9de
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Jun 21 18:22:26 2024 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Jun 21 18:22:26 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f6c02e98
app-i18n/poedit: Stabilize 2.3.1 amd64, #934657
Signed-off-by: Sam James <sam <AT> gentoo.org>
app-i18n/poedit/poedit-2.3.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-i18n/poedit/poedit-2.3.1.ebuild b/app-i18n/poedit/poedit-2.3.1.ebuild
index a9597b89f9fa..6905273c4f9e 100644
--- a/app-i18n/poedit/poedit-2.3.1.ebuild
+++ b/app-i18n/poedit/poedit-2.3.1.ebuild
@@ -12,7 +12,7 @@ DESCRIPTION="GUI gettext translations editor"
HOMEPAGE="https://poedit.net"
SRC_URI="https://github.com/vslavik/${PN}/releases/download/v${PV}-oss/${P}.tar.gz"
-KEYWORDS="~amd64 ~hppa ppc ppc64 ~sparc ~x86"
+KEYWORDS="amd64 ~hppa ppc ppc64 ~sparc ~x86"
LICENSE="MIT"
SLOT="0"
next reply other threads:[~2024-06-21 18:22 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 18:22 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-24 23:15 [gentoo-commits] repo/gentoo:master commit in: app-i18n/poedit/ Sam James
2024-11-08 18:16 Pacho Ramos
2024-11-08 18:16 Pacho Ramos
2024-08-30 14:59 Ionen Wolkens
2024-06-21 18:22 Sam James
2024-06-21 18:22 Sam James
2020-06-14 8:39 Mart Raudsepp
2019-12-31 8:18 Agostino Sarubbo
2019-12-31 8:15 Agostino Sarubbo
2019-12-30 12:29 Agostino Sarubbo
2019-12-28 10:17 Sergei Trofimovich
2019-12-27 16:43 Agostino Sarubbo
2019-12-25 21:24 Mart Raudsepp
2019-11-20 11:21 Agostino Sarubbo
2019-11-19 12:48 Agostino Sarubbo
2019-11-18 11:50 Agostino Sarubbo
2019-11-16 11:17 Mart Raudsepp
2019-11-16 11:17 Mart Raudsepp
2019-11-16 10:34 Sergei Trofimovich
2019-07-14 11:11 Mart Raudsepp
2018-12-20 0:20 Mart Raudsepp
2018-10-23 20:36 Sergei Trofimovich
2018-09-15 12:36 Mikle Kolyada
2018-09-11 20:45 Mart Raudsepp
2018-09-11 20:40 Matt Turner
2018-09-11 20:40 Matt Turner
2018-08-05 21:21 Mart Raudsepp
2018-08-05 1:03 Thomas Deutschmann
2018-08-04 0:07 Mikle Kolyada
2018-08-02 18:44 Sergei Trofimovich
2018-07-14 21:06 Mart Raudsepp
2018-05-27 9:40 Mart Raudsepp
2018-05-27 8:44 Mart Raudsepp
2018-04-20 19:48 David Seifert
2018-04-01 21:44 Sergei Trofimovich
2018-02-27 21:56 Sergei Trofimovich
2018-02-23 22:10 Sergei Trofimovich
2018-02-20 8:10 Sergei Trofimovich
2018-02-19 7:50 Jason Zaman
2018-02-18 21:48 Thomas Deutschmann
2018-02-10 12:56 Jeroen Roovers
2018-01-24 21:25 Sergei Trofimovich
2018-01-20 23:03 Andreas Sturmlechner
2018-01-20 19:13 Mart Raudsepp
2018-01-10 2:30 Mart Raudsepp
2017-12-23 19:53 Sergei Trofimovich
2017-12-23 19:53 Sergei Trofimovich
2017-12-10 14:16 David Seifert
2017-09-24 10:39 Sergei Trofimovich
2017-06-02 12:04 Jeroen Roovers
2017-04-22 14:03 Jeroen Roovers
2016-12-31 22:20 Agostino Sarubbo
2016-06-21 20:01 Michał Górny
2016-05-24 19:15 Pacho Ramos
2016-04-24 8:44 Ryan Hill
2015-10-15 2:19 Ryan Hill
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=1718994146.f6c02e98fa914521af64f810557700cccf63a9de.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