From: Glenn Washburn <development@efficientek.com>
To: grub-devel@gnu.org, Daniel Kiper <daniel.kiper@oracle.com>
Cc: Glenn Washburn <development@efficientek.com>
Subject: [PATCH 0/2] Misc doc changes
Date: Wed, 31 Mar 2021 19:11:51 -0500 [thread overview]
Message-ID: <cover.1617235760.git.development@efficientek.com> (raw)
The first patch adds a long overdue note to the cryptomount command that UUIDs
should be specified without dash, differently than how fs uuids are specified.
The second patch makes the indentation of command description text for cutmem
and badmem conform with the indentation of the rest of the commands.
Glenn
Glenn Washburn (2):
docs: Add note to cryptomount that UUIDs should be specified without
dashes
docs: Conform badmem and cutmem description indentations with other
commands
docs/grub.texi | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
--
2.27.0
next reply other threads:[~2021-04-01 0:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 0:11 Glenn Washburn [this message]
2021-04-01 0:11 ` [PATCH 1/2] docs: Add note to cryptomount that UUIDs should be specified without dashes Glenn Washburn
2021-04-01 0:11 ` [PATCH 2/2] docs: Conform badmem and cutmem description indentations with other commands Glenn Washburn
2021-04-08 16:53 ` [PATCH 0/2] Misc doc changes Daniel Kiper
2021-04-08 19:28 ` GRUB 2.06 Didier Spaier
2021-04-08 21:26 ` Didier Spaier
2021-04-20 13:53 ` Daniel Kiper
2021-04-20 14:00 ` John Paul Adrian Glaubitz
2021-04-20 17:34 ` Didier Spaier
2021-04-20 17:48 ` John Paul Adrian Glaubitz
2021-04-20 20:33 ` Eli Schwartz
2021-04-20 20:43 ` John Paul Adrian Glaubitz
2021-04-21 12:21 ` Daniel Kiper
2021-04-20 17:50 ` Mike Gilbert
2021-04-20 18:21 ` Bruce Dubbs
2021-04-20 18:36 ` Mike Gilbert
2021-04-20 18:43 ` John Paul Adrian Glaubitz
2021-04-20 19:58 ` Eli Schwartz
2021-04-21 12:27 ` Daniel Kiper
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=cover.1617235760.git.development@efficientek.com \
--to=development@efficientek.com \
--cc=daniel.kiper@oracle.com \
--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.