From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Daniel Kiper <daniel.kiper@oracle.com>,
grub-devel@gnu.org, xen-devel@lists.xenproject.org
Cc: andrew.cooper3@citrix.com, eric.snowberg@oracle.com,
jgross@suse.com, konrad.wilk@oracle.com, phcoder@gmail.com,
seth.goldberg@oracle.com
Subject: Re: [MULTIBOOT2 DOC PATCH v2 01/11] multiboot2: Rename Multiboot to Multiboot2
Date: Mon, 28 Nov 2016 21:06:32 +0300 [thread overview]
Message-ID: <f8d18ebf-7244-b51b-bdd3-cbc1ce100508@gmail.com> (raw)
In-Reply-To: <1480020010-18421-2-git-send-email-daniel.kiper@oracle.com>
24.11.2016 23:40, Daniel Kiper пишет:
> Multiboot2 is proper name of the boot protocol. Multiboot is name of older boot
> protocol. So, rename Multiboot to Multiboot2 to not confuse the reader.
>
> Signed-off-by: Daniel Kiper <daniel.kiper@oracle.com>
> ---
> doc/multiboot.texi | 112 ++++++++++++++++++++++++++--------------------------
What about file name itself? It makes it impossible for multiboot and
multiboot2 documentation to coexist (or forces every downstream to
rename it anyway).
next prev parent reply other threads:[~2016-11-28 18:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-24 20:39 [MULTIBOOT2 DOC PATCH v2 00/10] multiboot2: Update documentation Daniel Kiper
2016-11-24 20:40 ` [MULTIBOOT2 DOC PATCH v2 01/11] multiboot2: Rename Multiboot to Multiboot2 Daniel Kiper
2016-11-28 18:06 ` Andrei Borzenkov [this message]
2016-11-29 8:45 ` Daniel Kiper
2016-11-24 20:40 ` [MULTIBOOT2 DOC PATCH v2 02/11] multiboot2: Replace redundant if with the Daniel Kiper
2016-11-24 20:40 ` [MULTIBOOT2 DOC PATCH v2 03/11] multiboot2: Clarify meaning of information request header tag Daniel Kiper
2016-11-24 20:40 ` [MULTIBOOT2 DOC PATCH v2 04/11] multiboot2: Fix description of EFI boot services tag Daniel Kiper
2016-11-24 20:40 ` [MULTIBOOT2 DOC PATCH v2 05/11] multiboot2: Add description of support for EFI boot services Daniel Kiper
2016-11-24 21:47 ` Toomas Soome
2016-11-28 15:46 ` Daniel Kiper
2016-11-28 16:24 ` Toomas Soome
2016-11-28 17:53 ` Andrei Borzenkov
2016-11-29 9:08 ` Daniel Kiper
2016-11-29 9:39 ` Toomas Soome
2016-11-29 10:09 ` Daniel Kiper
2016-11-29 10:34 ` Toomas Soome
2016-11-24 20:40 ` [MULTIBOOT2 DOC PATCH v2 06/11] multiboot2: Add description of EFI image handle tags Daniel Kiper
2016-11-28 17:59 ` Andrei Borzenkov
2016-11-29 9:18 ` Daniel Kiper
2016-11-24 20:40 ` [MULTIBOOT2 DOC PATCH v2 07/11] multiboot2: Add description of support for relocatable images Daniel Kiper
2016-11-24 20:40 ` [MULTIBOOT2 DOC PATCH v2 08/11] multiboot2: Say that memory maps may not be available on EFI platforms Daniel Kiper
2016-11-24 20:40 ` [MULTIBOOT2 DOC PATCH v2 09/11] multiboot2: Add C structure members alignment and padding consideration section Daniel Kiper
2016-11-24 20:40 ` [MULTIBOOT2 DOC PATCH v2 10/11] multiboot2: Add me to authors Daniel Kiper
2016-11-24 20:40 ` [MULTIBOOT2 DOC PATCH v2 11/11] multiboot2: Bump version to 2.0 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=f8d18ebf-7244-b51b-bdd3-cbc1ce100508@gmail.com \
--to=arvidjaar@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=daniel.kiper@oracle.com \
--cc=eric.snowberg@oracle.com \
--cc=grub-devel@gnu.org \
--cc=jgross@suse.com \
--cc=konrad.wilk@oracle.com \
--cc=phcoder@gmail.com \
--cc=seth.goldberg@oracle.com \
--cc=xen-devel@lists.xenproject.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 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 NNTP newsgroup(s).