From: "Sergei Trofimovich" <slyfox@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-kernel/genkernel-next/
Date: Sat, 23 Feb 2019 11:58:35 +0000 (UTC) [thread overview]
Message-ID: <1550923105.4597498570113a6097da07739740ae36f2fcc79f.slyfox@gentoo> (raw)
commit: 4597498570113a6097da07739740ae36f2fcc79f
Author: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
AuthorDate: Sat Feb 23 11:57:12 2019 +0000
Commit: Sergei Trofimovich <slyfox <AT> gentoo <DOT> org>
CommitDate: Sat Feb 23 11:58:25 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=45974985
sys-kernel/genkernel-next: stable 69 for ppc, bug #672772
Package-Manager: Portage-2.3.62, Repoman-2.3.12
RepoMan-Options: --include-arches="ppc"
Signed-off-by: Sergei Trofimovich <slyfox <AT> gentoo.org>
sys-kernel/genkernel-next/genkernel-next-69.ebuild | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/sys-kernel/genkernel-next/genkernel-next-69.ebuild b/sys-kernel/genkernel-next/genkernel-next-69.ebuild
index 7ab1bf77da7..529b181df5f 100644
--- a/sys-kernel/genkernel-next/genkernel-next-69.ebuild
+++ b/sys-kernel/genkernel-next/genkernel-next-69.ebuild
@@ -4,7 +4,7 @@
EAPI=6
SRC_URI="https://github.com/Sabayon/genkernel-next/archive/v${PV}.tar.gz -> ${P}.tar.gz"
-KEYWORDS="~alpha amd64 ~arm ~hppa ~ia64 ~ppc ~ppc64 x86"
+KEYWORDS="~alpha amd64 ~arm ~hppa ~ia64 ppc ~ppc64 x86"
inherit bash-completion-r1
DESCRIPTION="Gentoo automatic kernel building scripts, reloaded"
next reply other threads:[~2019-02-23 11:58 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 11:58 Sergei Trofimovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-06-18 6:55 [gentoo-commits] repo/gentoo:master commit in: sys-kernel/genkernel-next/ Ettore Di Giacinto
2019-06-18 6:55 Ettore Di Giacinto
2019-06-05 7:28 Agostino Sarubbo
2019-04-09 12:06 Patrice Clement
2019-02-23 12:55 Sergei Trofimovich
2019-02-22 10:11 Mikle Kolyada
2019-02-20 21:50 Thomas Deutschmann
2018-11-25 12:13 Ettore Di Giacinto
2018-11-25 12:13 Ettore Di Giacinto
2018-03-20 22:26 Sergei Trofimovich
2018-03-18 19:55 Sergei Trofimovich
2018-03-11 1:04 Matt Turner
2018-03-10 12:53 Pacho Ramos
2018-02-10 10:35 Sergei Trofimovich
2018-02-01 20:37 Thomas Deutschmann
2017-11-26 22:25 Ettore Di Giacinto
2017-11-20 14:11 Manuel Rüger
2017-11-13 22:37 Sergei Trofimovich
2017-11-12 10:27 Sergei Trofimovich
2017-11-05 21:29 Thomas Deutschmann
2017-09-12 16:56 Ettore Di Giacinto
2017-09-12 16:56 Ettore Di Giacinto
2017-09-12 16:56 Ettore Di Giacinto
2017-09-05 21:51 Sergei Trofimovich
2017-09-04 20:45 Ettore Di Giacinto
2017-08-27 15:22 Michael Palimaka
2017-02-20 15:18 Ettore Di Giacinto
2017-01-17 15:52 Ettore Di Giacinto
2017-01-17 15:52 Ettore Di Giacinto
2016-12-25 2:44 Aaron Bauman
2016-11-06 20:39 Ettore Di Giacinto
2016-10-23 14:34 Ettore Di Giacinto
2016-07-30 14:35 Mike Gilbert
2016-07-06 9:23 Agostino Sarubbo
2016-06-10 15:32 Agostino Sarubbo
2016-05-29 14:38 Pacho Ramos
2016-05-29 14:37 Pacho Ramos
2016-05-29 14:37 Pacho Ramos
2016-04-16 18:27 Patrick Lauer
2016-04-16 14:57 Mikle Kolyada
2015-11-13 9:48 Agostino Sarubbo
2015-10-06 13:27 Mikle Kolyada
2015-08-16 20:38 Mikle Kolyada
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=1550923105.4597498570113a6097da07739740ae36f2fcc79f.slyfox@gentoo \
--to=slyfox@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