From: ludo@gnu.org (Ludovic Courtès)
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 27007@debbugs.gnu.org
Subject: bug#27007: boot-parameters are not documented
Date: Tue, 23 May 2017 14:24:54 +0200 [thread overview]
Message-ID: <87shjvsquh.fsf@gnu.org> (raw)
In-Reply-To: <86poezkdhl.fsf@gmail.com> (Mathieu Othacehe's message of "Tue, 23 May 2017 13:40:38 +0200")
Mathieu Othacehe <m.othacehe@gmail.com> skribis:
>> and those entries would be “lowered” to <boot-parameters> somewhere.
>> That way we’d provide the abstraction level that users may expect (“how
>> do I add a menu entry for my other distro?”) and at the same time reduce
>> the risk of mistakes (“I didn’t what to put in ‘store-device’ I put my
>> pet’s name there”).
>>
>> WDYT? :-)
>>
>
> It seems fine ! So to summarize, <menu-entry> would be moved to (gnu
> bootloader). A procedure menu-entry->boot-parameters would assure
> the mapping in (gnu bootloader).
>
> Each booloader in (gnu bootloader xxx), would add
> bootloader-configuration-menu-entries to generated entries.
>
> I'll be afk for a week, but I'll submit a patch and the updated
> documentation for this point when coming back.
Sounds like a good plan, thank you!
Ludo’.
next prev parent reply other threads:[~2017-05-23 12:26 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 20:00 bug#27007: boot-parameters are not documented Tomáš Čech
2017-05-20 20:31 ` Mathieu Othacehe
2017-05-20 21:07 ` Leo Famulari
2017-05-20 21:43 ` Tomáš Čech
2017-05-20 20:52 ` Danny Milosavljevic
2017-05-20 21:00 ` Tomáš Čech
2017-05-22 15:55 ` Ludovic Courtès
2017-05-22 17:31 ` Mathieu Othacehe
2017-05-23 8:13 ` Ludovic Courtès
2017-05-23 9:31 ` Mathieu Othacehe
2017-05-23 9:57 ` Tomáš Čech
2017-05-23 11:23 ` Ludovic Courtès
2017-05-23 11:40 ` Mathieu Othacehe
2017-05-23 12:24 ` Ludovic Courtès [this message]
2017-05-31 7:23 ` bug#27007: [PATCH 0/2] Use menu-entry to define custom bootloader entries Mathieu Othacehe
2017-05-31 7:23 ` bug#27007: [PATCH 1/2] bootloader: " Mathieu Othacehe
2017-05-31 22:11 ` Danny Milosavljevic
2017-06-01 8:34 ` Mathieu Othacehe
2017-06-01 11:14 ` Danny Milosavljevic
2017-06-02 9:29 ` Mathieu Othacehe
2017-06-02 14:30 ` Marius Bakke
2017-06-01 11:22 ` Ludovic Courtès
2017-06-05 10:23 ` Ludovic Courtès
2017-06-06 8:14 ` Mathieu Othacehe
2017-05-31 7:23 ` bug#27007: [PATCH 2/2] doc: Adapt to multiple bootloader support Mathieu Othacehe
2017-05-31 21:57 ` Danny Milosavljevic
2017-06-05 10:38 ` Ludovic Courtès
2017-06-05 10:36 ` Ludovic Courtès
2017-06-05 14:11 ` Danny Milosavljevic
2017-06-06 22:51 ` Ludovic Courtès
2017-06-08 10:59 ` Mathieu Othacehe
2017-06-06 9:20 ` Mathieu Othacehe
2017-05-24 20:11 ` bug#27007: boot-parameters are not documented Danny Milosavljevic
2017-05-26 8:47 ` Ludovic Courtès
2017-05-26 9:03 ` ng0
2017-06-08 10:57 ` bug#27007: [PATCH v2 1/2] bootloader: Use menu-entry to define custom bootloader entries Mathieu Othacehe
2017-06-08 10:57 ` bug#27007: [PATCH v2 2/2] doc: Adapt to multiple bootloader support Mathieu Othacehe
2017-06-08 12:39 ` Ludovic Courtès
2017-06-08 14:33 ` Mathieu Othacehe
2017-06-08 12:36 ` bug#27007: [PATCH v2 1/2] bootloader: Use menu-entry to define custom bootloader entries 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=87shjvsquh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=27007@debbugs.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).