unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH WIP] linux-initrd: Add a raw-initrd and use it to define base-initrd.
Date: Wed, 08 Mar 2017 18:28:44 +0100	[thread overview]
Message-ID: <874lz3lltf.fsf@gnu.org> (raw)
In-Reply-To: <20170307082455.3159-1-m.othacehe@gmail.com> (Mathieu Othacehe's message of "Tue, 7 Mar 2017 09:24:55 +0100")

Hi Mathieu,

Mathieu Othacehe <m.othacehe@gmail.com> skribis:

> * gnu/system/linux-initrd.scm (raw-initrd): New exported variable.
> (base-initrd): Use raw-initrd to build the initrd.

Nice!

> It has been discussed here :
> https://lists.gnu.org/archive/html/guix-devel/2016-07/msg01524.html
> and here :
> https://lists.gnu.org/archive/html/guix-devel/2017-02/msg00937.html
>
> As a summary, it is useful if you have a custom kernel config and base-initrd tries
> to include not compiled modules for example.
>
> raw-initrd doesn't try neither to guess which helper-packages should be included
> in the initrd. I'm not sure this is the right thing to do here.
>
> Note I didn't update the doc yet as this is still a draft patch.
>
> What do you think ?

I think it looks good, and definitely an improvement.

So the remaining bits would be:

  1. Making sure ‘make check-system TESTS=basic’ or similar works.

  2. Adding a copyright line for you.  :-)

  3. Updating the doc.

Could you send an updated patch?

Thanks for working on it!

Ludo’.

  reply	other threads:[~2017-03-08 17:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-07  8:24 [PATCH WIP] linux-initrd: Add a raw-initrd and use it to define base-initrd Mathieu Othacehe
2017-03-08 17:28 ` Ludovic Courtès [this message]
2017-03-09 18:39   ` [PATCH] " Mathieu Othacehe
2017-03-10 16:03     ` Ludovic Courtès

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=874lz3lltf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=m.othacehe@gmail.com \
    /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).