From: Nicolas Bock <nicolasbock@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] vanilla-sources broken
Date: Fri, 5 Jan 2018 07:56:55 -0700 [thread overview]
Message-ID: <20180105145655.7hhe64dsbwzl24tx@rubberducky> (raw)
In-Reply-To: <CANWzcUqHjN82Ntd+w=JfKqHctTtAxYbr1o6iUBueC4BDGXvkEA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]
On Fri, Jan 05, 2018 at 11:47:51PM +0900, Alice Ferrazzi wrote:
>On Fri, Jan 5, 2018 at 11:08 PM, Nicolas Bock <nicolasbock@gentoo.org> wrote:
>> Hi,
>>
>> currently vanilla-sources are broken, but there is an upstream patch that
>> fixes it (appended at the end). I know that vanilla-sources are supposed to
>> be vanilla, but it would help if we added this patch until upstream
>> backports it. Any thoughts?
>>
Thanks Alice,
I'll try my luck upstream :)
Nick
>Hello Nicolas,
>
>vanilla-sources, unfortunately, are given same as the kernel upstream,
>Gentoo is not supporting or adding patches to vanilla-sources.
>If you have any problem with vanilla-sources please report it to the Kernel
>upstream not to Gentoo.
>If you want kernel support from Gentoo kernel team, please switch to
>gentoo-sources.
>
>--
>Thanks,
>Alice Ferrazzi
>
>Gentoo Kernel Project Leader
>Gentoo Foundation Board Member
>Mail: Alice Ferrazzi <alicef@gentoo.org>
>PGP: 2E4E 0856 461C 0585 1336 F496 5621 A6B2 8638 781A
>
--
Nicolas Bock <nicolasbock@gentoo.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2018-01-05 14:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 14:08 [gentoo-dev] vanilla-sources broken Nicolas Bock
2018-01-05 14:47 ` Alice Ferrazzi
2018-01-05 14:56 ` Nicolas Bock [this message]
2018-01-16 14:38 ` [gentoo-dev] " Holger Hoffstätte
2018-01-16 16:24 ` Nicolas Bock
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=20180105145655.7hhe64dsbwzl24tx@rubberducky \
--to=nicolasbock@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