Re: [PATCH v4] templates: introduce GRUB_TOP_LEVEL_* vars
Olaf Hering <[email protected]> Thu, 20 Oct 2022 17:13:06 +0200
| Newsgroups | gmane.comp.emulators.xen.devel,gmane.comp.boot-loaders.grub.devel,gmane.linux.debian.ports.bsd |
|---|---|
| Message-ID | <[email protected]> |
Tue, 18 Oct 2022 21:53:32 -0700 Denton Liu <[email protected]>: > On Tue, Oct 18, 2022 at 04:18:21PM +0200, Olaf Hering wrote: > > Maybe the patch description lacks a specific example how the proposed change is supposed to be used in your environment. > My patch description says: > Introduce the GRUB_TOP_LEVEL, GRUB_TOP_LEVEL_XEN and > GRUB_TOP_LEVEL_OS_PROBER variables to allow users to specify the > top-level entry. > and I'm not quite sure how to make it more clear other than, perhaps, > explaining what the top-level entry means. After reading the patch again, the newly added documentation states: "This option should be a path to a kernel image." I think it needs to be more specific: is it expecting an absolute path, or just the basename of the desired image? Olaf
signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE97o7Um30LT3B+5b/86SN7mm1DoAFAmNRZYIACgkQ86SN7mm1 DoBewg/8CgSvlpBoJ4+VNyZOEvHOQF4y5qQkB5WhitIv3GmEztNrEYtLe4lo5MYf q/TcIK1B5VMo1axI8E0YZRvDD2e0++DaBBVH/8+MokgLKyMTHRuLAVwwxYXLdHId hnWjaB19Z8pJSXddeoDxg0WSDZI881478+zoKA+oOaQPRX/rkxYQ8AodEgPnNNk8 n747EzPB0rFGhVS6/lPJKWrmLJeApr8LgDmhKao/ECrfoekQGxfGTYoPWrFnA7Fp qS/cHBd/cGi6NeCRay6zGgmMQn4B6CqRy62tozAEUS9W9lvibFuL2poH2gnUBflt WCmFl3K+2CHTZwXg0SQ24LOc3JW3OPccOZMGJoMIGnHNWx9PC6M96/lHNn+8l+jy mYqyggMvfFYJCI6eHAkmCp6/hTamSDFWpRKjm9HmVdcSuoYSNIp69eJulAkVewjO AJd0vrqe1k+Qfdl1H7x31+iRKvw4nwdsZweSW8sVG7oHOuQS9Zj/w6C6NtDNNvc5 BB1P2XUgrmKkJxm+b66KCUUAB6N14KOBmHAIbKeqJ7j6xRMBi1s+9bkz72zXxX// HiX0mboyTHE1hUHCSlnZmkMkO7dEsfGXC9F2KHEKulSXXuo64lByjRltcQT5C7sy p+P616d6yKHk1GlDGX63q6T9za2mmcz/y+g+n6DDlEGnH4+x/2Q= =eJ4i -----END PGP SIGNATURE-----