unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: Carl Dong <accounts@carldong.me>, guix-devel@gnu.org
Subject: Re: 01/01: gnu: Use make-linux-libre-headers.
Date: Thu, 30 May 2019 17:35:44 -0400	[thread overview]
Message-ID: <87ftovpqus.fsf@netris.org> (raw)
In-Reply-To: <20190530103143.08ba1074@scratchpost.org> (Danny Milosavljevic's message of "Thu, 30 May 2019 10:31:43 +0200")

Hi Danny,

Danny Milosavljevic <dannym@scratchpost.org> writes:

>> I think we should not add linux-libre-4.15, because that version of
>> Linux-libre is no longer supported upstream, and therefore will have
>> well-known security flaws.
>
> OK with me to remove.
>
> The headers were from 4.14.67 (and still are), though.  So we'll have
> headers which we don't have a Linux kernel for.  (Since those change
> very rarely, that's not such a big deal)

Hmm, I don't understand.  What do the 4.14.x headers have to do with
4.15, which is the version I'm suggesting to delete?

>> Also, this removes the definition of 'linux-libre', which I, for one,
>> reference from my OS config and maybe others do as well.  Sometimes it's
>> useful to break compatibility, but in this case I see no reason for it.
>
> It doesn't.  I think I messed up the commit *message*, but there is a
> definition of linux-libre still (as before).

Indeed, you're right about this, my mistake.

     Thanks,
       Mark

  reply	other threads:[~2019-05-30 21:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190529163123.3417.15650@vcs0.savannah.gnu.org>
     [not found] ` <20190529163123.ECCE2209A5@vcs0.savannah.gnu.org>
2019-05-30  1:31   ` 01/01: gnu: Use make-linux-libre-headers Mark H Weaver
2019-05-30  2:04     ` Carl Dong
2019-05-30  8:31     ` Danny Milosavljevic
2019-05-30 21:35       ` Mark H Weaver [this message]
2019-05-30 22:13         ` Danny Milosavljevic

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=87ftovpqus.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=accounts@carldong.me \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@gnu.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).