From: "Agostino Sarubbo" <ago@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-vcs/hg-git/
Date: Mon, 7 Jun 2021 13:16:59 +0000 (UTC) [thread overview]
Message-ID: <1623071790.b5301b7cac51cb49a9a533364463be382d89a800.ago@gentoo> (raw)
commit: b5301b7cac51cb49a9a533364463be382d89a800
Author: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
AuthorDate: Mon Jun 7 13:16:30 2021 +0000
Commit: Agostino Sarubbo <ago <AT> gentoo <DOT> org>
CommitDate: Mon Jun 7 13:16:30 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=b5301b7c
dev-vcs/hg-git: ppc stable wrt bug #793842
Package-Manager: Portage-3.0.13, Repoman-3.0.2
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Agostino Sarubbo <ago <AT> gentoo.org>
dev-vcs/hg-git/hg-git-0.9.0.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/dev-vcs/hg-git/hg-git-0.9.0.ebuild b/dev-vcs/hg-git/hg-git-0.9.0.ebuild
index 88d584e3f0d..029e0337496 100644
--- a/dev-vcs/hg-git/hg-git-0.9.0.ebuild
+++ b/dev-vcs/hg-git/hg-git-0.9.0.ebuild
@@ -14,7 +14,7 @@ SRC_URI="https://foss.heptapod.net/mercurial/hg-git/-/archive/${MY_PV}/${PN}-${M
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="amd64 ~ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
+KEYWORDS="amd64 ppc ~ppc64 ~x86 ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
IUSE=""
RDEPEND="
next reply other threads:[~2021-06-07 13:17 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-07 13:16 Agostino Sarubbo [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-10 18:47 [gentoo-commits] repo/gentoo:master commit in: dev-vcs/hg-git/ Arthur Zamarin
2024-09-10 18:24 Mike Gilbert
2024-09-10 17:50 Fabian Groffen
2024-06-29 14:47 Arthur Zamarin
2024-05-12 8:59 Fabian Groffen
2023-09-10 10:41 Fabian Groffen
2023-05-01 0:19 Sam James
2023-05-01 0:12 Sam James
2023-05-01 0:09 Sam James
2023-03-08 7:48 Fabian Groffen
2023-02-25 10:18 Fabian Groffen
2022-11-15 18:17 Michał Górny
2022-07-03 10:52 Agostino Sarubbo
2022-07-03 10:49 Agostino Sarubbo
2022-07-03 10:48 Agostino Sarubbo
2022-01-07 15:25 Fabian Groffen
2021-09-22 17:05 Fabian Groffen
2021-06-05 20:43 Sam James
2021-06-05 6:51 Fabian Groffen
2021-06-05 6:45 Fabian Groffen
2021-01-06 22:58 Fabian Groffen
2020-09-20 9:43 Fabian Groffen
2020-09-19 21:33 Michał Górny
2020-09-19 21:33 Michał Górny
2020-09-19 17:16 Sam James
2020-05-30 20:06 Fabian Groffen
2020-04-25 18:03 Fabian Groffen
2020-02-02 13:13 Fabian Groffen
2019-11-03 12:42 Fabian Groffen
2019-11-03 10:41 Fabian Groffen
2018-10-27 7:51 Fabian Groffen
2018-10-27 7:51 Fabian Groffen
2018-05-20 19:59 Fabian Groffen
2018-03-03 21:07 Sergei Trofimovich
2018-01-25 3:07 Aaron Bauman
2017-12-19 7:51 Fabian Groffen
2017-12-16 8:20 Tobias Klausmann
2017-11-13 18:39 Fabian Groffen
2017-11-09 13:27 Thomas Deutschmann
2017-09-19 7:01 Fabian Groffen
2017-08-03 7:34 Fabian Groffen
2017-06-10 19:32 Fabian Groffen
2017-05-24 19:47 Fabian Groffen
2017-04-27 10:55 Dirkjan Ochtman
2016-05-13 8:41 Agostino Sarubbo
2016-02-20 10:44 Dirkjan Ochtman
2016-01-18 9:39 Mike Frysinger
2015-12-28 21:21 Dirkjan Ochtman
2015-12-28 21:21 Dirkjan Ochtman
2015-09-19 9:48 Dirkjan Ochtman
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=1623071790.b5301b7cac51cb49a9a533364463be382d89a800.ago@gentoo \
--to=ago@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