From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] genkernel-next instead of genkernel?
Date: Fri, 16 Dec 2016 14:30:59 -0500 [thread overview]
Message-ID: <20161216193059.GH10558@vapier.lan> (raw)
In-Reply-To: <CY4PR06MB27928FA96113A74A74672CB89EC40@CY4PR06MB2792.namprd06.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 183 bytes --]
the chances of catalyst switching to genkernel-next is pretty low
to non-existent. they forked an old version of genkernel and dropped
support for things like cross-compiling.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-12-16 19:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-05 21:29 [gentoo-catalyst] genkernel-next instead of genkernel? Kuzminsky, Sebastian
2016-12-16 19:30 ` Mike Frysinger [this message]
2016-12-16 20:13 ` Leno Hou
2016-12-19 5:23 ` Marshall McMullen
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=20161216193059.GH10558@vapier.lan \
--to=vapier@gentoo.org \
--cc=gentoo-catalyst@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