From: Oskari Pirhonen <xxc3ncoredxx@gmail.com>
To: darkpenguin <darkpenguin@posteo.de>
Cc: grub-devel@gnu.org
Subject: Re: [PATCH] Allow specifying the boot device by its label instead of UUID
Date: Thu, 28 Sep 2023 00:16:43 -0500 [thread overview]
Message-ID: <ZRUMO9mLyQLBYBNs@dj3ntoo> (raw)
In-Reply-To: <20230927162523.664433-1-darkpenguin@posteo.de>
[-- Attachment #1.1: Type: text/plain, Size: 1437 bytes --]
I know you're just learning, so here's some more tips:
Updated patches are generally sent as a "vN" where N is the revision of
the series. `git format-patch` can do this nicely with the `-v` arg.
This would make the subject line look like "[PATCH vN] Allow specifying
the boot device by its label instead of UUID".
Updated patches are also typically sent as a new thread instead of as a
reply to the old one. Makes for easier review.
On Wed, Sep 27, 2023 at 16:25:23 +0000, darkpenguin wrote:
> Here it is, as a single patch, and in reply to the corresponding thread this time!
>
The way git handles patches, applying this would make the above sentence
the commit message. Which is probably not what you were after.
> ---
> util/grub-mkconfig.in | 1 +
> util/grub-mkconfig_lib.in | 14 +++++++++++---
> util/grub.d/10_linux.in | 3 +++
> 3 files changed, 15 insertions(+), 3 deletions(-)
>
> diff --git a/util/grub-mkconfig.in b/util/grub-mkconfig.in
> index 32c480dae..fb5000d3f 100644
> --- a/util/grub-mkconfig.in
> +++ b/util/grub-mkconfig.in
> @@ -244,6 +244,7 @@ export GRUB_DEFAULT \
> GRUB_DISABLE_UUID \
> GRUB_DISABLE_LINUX_UUID \
> GRUB_DISABLE_LINUX_PARTUUID \
> + GRUB_ENABLE_LINUX_LABEL \
I still think this should be GRUB_DISABLE_LINUX_LABEL to match the other
vars.
> GRUB_DISABLE_RECOVERY \
> GRUB_VIDEO_BACKEND \
> GRUB_GFXMODE \
- Oskari
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 141 bytes --]
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next prev parent reply other threads:[~2023-09-28 5:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 11:13 [PATCH 0/2] Add support for specifying the boot device by label darkpenguin
2023-09-27 11:13 ` [PATCH 1/2] Allow specifying the boot device by its label instead of UUID darkpenguin
2023-09-27 15:50 ` Vladimir 'phcoder' Serbinenko
2023-09-27 16:02 ` darkpenguin
2023-09-27 16:18 ` Heinrich Schuchardt
2023-09-27 16:25 ` [PATCH] " darkpenguin
2023-09-27 20:41 ` Vladimir 'phcoder' Serbinenko
2023-09-28 5:16 ` Oskari Pirhonen [this message]
2023-09-28 8:05 ` darkpenguin
2023-09-27 11:13 ` [PATCH 2/2] Use GRUB_ENABLE_LINUX_LABEL=true instead of GRUB_DISABLE_LINUX_UUID=LABEL darkpenguin
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZRUMO9mLyQLBYBNs@dj3ntoo \
--to=xxc3ncoredxx@gmail.com \
--cc=darkpenguin@posteo.de \
--cc=grub-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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.