From: "Mart Raudsepp" <leio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: www-apps/cgit/
Date: Tue, 7 Aug 2018 23:01:47 +0000 (UTC) [thread overview]
Message-ID: <1533682886.18f5895a6a36355857f2dbf4a3cff6f040f5b810.leio@gentoo> (raw)
commit: 18f5895a6a36355857f2dbf4a3cff6f040f5b810
Author: Mart Raudsepp <leio <AT> gentoo <DOT> org>
AuthorDate: Tue Aug 7 19:13:15 2018 +0000
Commit: Mart Raudsepp <leio <AT> gentoo <DOT> org>
CommitDate: Tue Aug 7 23:01:26 2018 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=18f5895a
www-apps/cgit: remove randomly and very wrongly added arm64 keyword
cgit didn't even have ~arm64 keywords, yet was stabled out of the blue,
leading to a broken deptree QA issues.
Package-Manager: Portage-2.3.43, Repoman-2.3.10
www-apps/cgit/cgit-1.2.1.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/www-apps/cgit/cgit-1.2.1.ebuild b/www-apps/cgit/cgit-1.2.1.ebuild
index 47dca91a09f..82174c82295 100644
--- a/www-apps/cgit/cgit-1.2.1.ebuild
+++ b/www-apps/cgit/cgit-1.2.1.ebuild
@@ -18,7 +18,7 @@ SRC_URI="mirror://kernel/software/scm/git/git-${GIT_V}.tar.xz
LICENSE="GPL-2"
SLOT="0"
-KEYWORDS="amd64 arm arm64 x86"
+KEYWORDS="amd64 arm x86"
IUSE="doc +highlight +lua +jit"
RDEPEND="
next reply other threads:[~2018-08-07 23:01 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 23:01 Mart Raudsepp [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-18 13:57 [gentoo-commits] repo/gentoo:master commit in: www-apps/cgit/ Sam James
2025-03-18 13:57 Sam James
2024-05-29 17:37 Sam James
2024-05-29 11:47 Sam James
2024-05-29 6:26 Jakov Smolić
2024-05-08 3:15 Robin H. Johnson
2024-04-15 17:44 Viorel Munteanu
2023-04-25 2:22 Sam James
2022-10-24 22:52 Yixun Lan
2022-10-20 10:56 Jakov Smolić
2022-10-20 10:52 Jakov Smolić
2022-10-16 8:54 Agostino Sarubbo
2022-10-15 15:13 Sam James
2022-07-29 18:57 Matt Turner
2022-07-29 18:57 Matt Turner
2022-07-29 18:57 Matt Turner
2021-05-02 8:08 Mikle Kolyada
2021-02-07 23:00 Aaron Bauman
2021-01-25 17:38 Marek Szuba
2021-01-23 22:51 Sam James
2021-01-23 4:20 Sam James
2021-01-23 4:09 Sam James
2020-11-27 20:16 Aaron Bauman
2020-11-27 20:11 Aaron Bauman
2020-03-23 22:35 Matt Turner
2020-03-23 22:35 Matt Turner
2020-03-23 22:19 Matt Turner
2020-03-23 22:19 Matt Turner
2020-03-14 3:26 Jason A. Donenfeld
2020-01-13 20:53 Jason A. Donenfeld
2020-01-02 3:02 Stefan Strogin
2019-12-16 9:39 Michał Górny
2019-12-15 20:42 Michał Górny
2019-10-05 18:56 Michał Górny
2019-09-29 20:59 Ben Kohler
2018-08-04 14:53 Jason Donenfeld
2018-08-03 15:14 Jason Donenfeld
2018-07-13 22:30 Jason Donenfeld
2018-05-18 12:34 Aaron Bauman
2017-04-05 13:45 Michael Weber
2017-02-12 17:37 Robin H. Johnson
2016-02-22 18:20 Jason Donenfeld
2016-02-12 3:38 Jason Donenfeld
2016-01-14 14:52 Jason Donenfeld
2016-01-14 14:51 Jason Donenfeld
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=1533682886.18f5895a6a36355857f2dbf4a3cff6f040f5b810.leio@gentoo \
--to=leio@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