From: Yasuaki Kudo <yasu@yasuaki.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: linux-libre updates, timeliness
Date: Wed, 7 Oct 2020 06:32:34 +0900 [thread overview]
Message-ID: <C5D2F80A-00DD-4F71-A46C-1CA1FEEF2C77@yasuaki.com> (raw)
In-Reply-To: <20201006144812.GA21955@jasmine.lan>
[-- Attachment #1: Type: text/plain, Size: 1102 bytes --]
Sorry, I meant to ask really a simple question because I just wanted to understand LinuxLibre. 😄 There is an explanation here:
https://en.m.wikipedia.org/wiki/Linux-libre
But I was intrigued, that it felt like a situation where a vegetarian would order a pizza from a restaurant that doesn't offer a vegetarian option so he has to painstakingly remove meat from it, while it would have been better if the cook could make it without the meat in the first place 😄
Is above a fair analogy for the Linux Kernel?
Cheers,
Yasu
> On Oct 6, 2020, at 23:48, Leo Famulari <leo@famulari.name> wrote:
>
> On Tue, Oct 06, 2020 at 06:12:15AM +0900, Yasuaki Kudo wrote:
>> Just out of curiosity, is it the case if only Linux Kernel team itself
>> separated the controversial (with GNU folks, at least 😄) aspect of
>> Linux as some build option, we don't have to maintain this
>> "LinuxLibre" in the first place?
>
> If you are asking if linux-libre is slowing down the process of updating
> the kernel for Guix users, the answer is that it's not a significant
> delay.
[-- Attachment #2: Type: text/html, Size: 1906 bytes --]
next prev parent reply other threads:[~2020-10-06 21:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 22:45 linux-libre updates, timeliness Leo Famulari
2020-10-05 13:53 ` Ludovic Courtès
2020-10-05 21:12 ` Yasuaki Kudo
2020-10-06 14:48 ` Leo Famulari
2020-10-06 21:32 ` Yasuaki Kudo [this message]
2020-10-09 19:54 ` Leo Famulari
2020-10-06 14:49 ` Leo Famulari
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C5D2F80A-00DD-4F71-A46C-1CA1FEEF2C77@yasuaki.com \
--to=yasu@yasuaki.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).