From: Mark H Weaver <mhw@netris.org>
To: Alexandre Oliva <lxoliva@fsfla.org>
Cc: guix-devel@gnu.org, Jason Self <jason@bluehome.net>
Subject: Re: Linux-libre 5.8 and beyond
Date: Sat, 15 Aug 2020 21:24:08 -0400 [thread overview]
Message-ID: <87d03rgz70.fsf@netris.org> (raw)
In-Reply-To: <875z9kv41h.fsf@netris.org>
Hi Alexandre,
I thought about it some more, and I've changed my mind on one point:
I've decided that for future kernel updates, in order to eliminate the
risk of unintentionally allowing blobs into Guix, I will either wait for
Linux-libre to publish updated deblob scripts, or else I will manually
check for new blobs.
Thanks,
Mark
next prev parent reply other threads:[~2020-08-16 1:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-09 20:15 Linux-libre 5.8 and beyond Jason Self
2020-08-13 0:39 ` Mark H Weaver
2020-08-13 16:47 ` Linux-libre git repository Vagrant Cascadian
2020-08-14 0:03 ` Jason Self
2020-08-14 14:03 ` Danny Milosavljevic
2020-08-14 13:47 ` Linux-libre 5.8 and beyond Alexandre Oliva
2020-08-15 6:03 ` Mark H Weaver
2020-08-16 1:24 ` Mark H Weaver [this message]
2020-08-16 12:43 ` Jason Self
2020-08-16 10:54 ` Jason Self
2020-08-24 3:45 ` Alexandre Oliva
2020-08-25 4:14 ` Mark H Weaver
2020-08-25 11:12 ` Alexandre Oliva
2020-08-24 3:58 ` Alexandre Oliva
2020-08-24 4:12 ` Alexandre Oliva
2020-08-24 4:34 ` Alexandre Oliva
2020-08-24 4:42 ` Alexandre Oliva
-- strict thread matches above, loose matches on Subject: below --
2020-08-11 4:07 Mark H Weaver
2020-08-08 20:57 Vagrant Cascadian
2020-08-09 0:02 ` Mark H Weaver
2020-08-09 3:30 ` Mark H Weaver
2020-08-09 3:43 ` Vagrant Cascadian
2020-08-09 18:09 ` Vagrant Cascadian
2020-08-09 22:17 ` Mark H Weaver
2020-08-10 22:39 ` Bengt Richter
2020-08-11 2:37 ` Tobias Geerinckx-Rice
2020-08-09 18:49 ` Leo Famulari
2020-08-25 21:01 ` Leo Famulari
2020-08-26 3:17 ` Leo Famulari
2020-08-26 15:41 ` Katherine Cox-Buday
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=87d03rgz70.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=jason@bluehome.net \
--cc=lxoliva@fsfla.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.
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).