From: "Mikle Kolyada" <zlogene@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-editors/ghex/
Date: Sat, 31 Aug 2019 05:26:32 +0000 (UTC) [thread overview]
Message-ID: <1567228984.c5e84e88c34d344d66e3e9d7c2eb948118e72a80.zlogene@gentoo> (raw)
commit: c5e84e88c34d344d66e3e9d7c2eb948118e72a80
Author: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
AuthorDate: Sat Aug 31 05:23:04 2019 +0000
Commit: Mikle Kolyada <zlogene <AT> gentoo <DOT> org>
CommitDate: Sat Aug 31 05:23:04 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c5e84e88
app-editors/ghex: amd64 stable wrt bug #692932
Package-Manager: Portage-2.3.69, Repoman-2.3.16
RepoMan-Options: --include-arches="amd64"
Signed-off-by: Mikle Kolyada <zlogene <AT> gentoo.org>
app-editors/ghex/ghex-3.18.4-r1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/app-editors/ghex/ghex-3.18.4-r1.ebuild b/app-editors/ghex/ghex-3.18.4-r1.ebuild
index a735e8d30a0..8e81590e73b 100644
--- a/app-editors/ghex/ghex-3.18.4-r1.ebuild
+++ b/app-editors/ghex/ghex-3.18.4-r1.ebuild
@@ -8,7 +8,7 @@ HOMEPAGE="https://wiki.gnome.org/Apps/Ghex"
LICENSE="GPL-2+ FDL-1.1+"
SLOT="2"
-KEYWORDS="~amd64 ~arm ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux"
+KEYWORDS="amd64 ~arm ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux"
IUSE=""
RDEPEND="
next reply other threads:[~2019-08-31 5:26 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-31 5:26 Mikle Kolyada [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-16 10:55 [gentoo-commits] repo/gentoo:master commit in: app-editors/ghex/ Pacho Ramos
2024-07-16 10:55 Pacho Ramos
2024-07-16 10:55 Pacho Ramos
2024-07-16 10:55 Pacho Ramos
2024-04-13 10:37 Mart Raudsepp
2024-04-13 10:37 Mart Raudsepp
2024-04-07 6:25 Arthur Zamarin
2024-03-24 20:46 Mart Raudsepp
2023-10-19 14:53 Pacho Ramos
2023-10-19 14:53 Pacho Ramos
2023-10-03 17:21 Mart Raudsepp
2023-09-01 16:07 Arthur Zamarin
2023-08-18 14:50 Matt Turner
2023-05-04 16:15 Arthur Zamarin
2023-05-03 3:53 Sam James
2023-05-02 19:46 Arthur Zamarin
2023-05-02 18:24 Arthur Zamarin
2023-04-28 0:28 Matt Turner
2023-04-01 19:01 Arthur Zamarin
2023-03-24 23:21 Matt Turner
2023-03-12 17:38 Matt Turner
2023-02-10 19:18 Matt Turner
2022-10-29 22:33 Matt Turner
2022-10-06 2:03 Matt Turner
2022-10-06 2:03 Matt Turner
2022-07-21 0:13 Sam James
2022-06-14 2:49 Matt Turner
2022-05-07 18:28 Arthur Zamarin
2022-05-07 18:25 Arthur Zamarin
2022-04-28 15:31 Matt Turner
2022-04-17 21:34 Matt Turner
2022-04-07 17:04 Matt Turner
2022-04-07 4:42 Matt Turner
2022-03-09 12:49 Sam James
2021-12-24 0:53 Jonas Stein
2021-12-19 5:01 Matt Turner
2020-11-27 16:10 Agostino Sarubbo
2020-11-27 16:08 Agostino Sarubbo
2019-09-08 10:47 Mart Raudsepp
2019-09-08 1:13 Thomas Deutschmann
2019-07-16 19:06 Mart Raudsepp
2019-07-15 19:55 Michał Górny
2019-07-15 3:14 Sobhan Mohammadpour
2019-07-14 23:19 Sobhan Mohammadpour
2018-10-14 9:09 Sergei Trofimovich
2017-02-15 16:57 Mart Raudsepp
2017-01-29 14:38 Fabian Groffen
2016-10-15 15:42 Gilles Dartiguelongue
2016-10-15 15:42 Gilles Dartiguelongue
2016-07-02 10:43 Pacho Ramos
2016-05-29 14:48 Pacho Ramos
2016-05-28 15:49 Pacho Ramos
2016-05-28 15:49 Pacho Ramos
2015-11-14 15:27 Pacho Ramos
2015-10-24 8:08 Pacho Ramos
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=1567228984.c5e84e88c34d344d66e3e9d7c2eb948118e72a80.zlogene@gentoo \
--to=zlogene@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