From: Simon Marchi <simon.marchi@polymtl.ca>
To: Eli Zaretskii <eliz@gnu.org>, Simon Marchi <simon.marchi@efficios.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/2] gdb/doc: rename "x86 Architecture-specific Issues" section to "x86"
Date: Fri, 8 Sep 2023 13:17:53 -0400 [thread overview]
Message-ID: <8e583748-66dc-49b4-b138-e197a68b2718@polymtl.ca> (raw)
In-Reply-To: <83h6o4wuak.fsf@gnu.org>
On 9/8/23 11:37, Eli Zaretskii via Gdb-patches wrote:
>> Cc: Simon Marchi <simon.marchi@efficios.com>
>> Date: Fri, 8 Sep 2023 11:20:57 -0400
>> From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
>>
>> I'm looking to add some x86-specific information to the doc, but I find
>> the naming of this section odd. It doesn't really talk about issues, it
>> just gives generally useful information. Also, the sections about other
>> architectures don't mention "issues", just the architecture name.
>>
>> Also, at least in the HTML version of the doc, the name is inconsistent
>> between the main table of content, where it appears as "x86
>> Architecture-specific Issues", and the sub-table of contents of the
>> "Architectures" section, where it appears as "i386".
>>
>> Rename the section to just "x86".
>
> Assuming the information there is good for x86_64 as well, this is
> fine by me.
I think it is.
> Approved-By: Eli Zaretskii <eliz@gnu.org>
Thanks, pushed.
Simon
prev parent reply other threads:[~2023-09-08 17:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-08 15:20 Simon Marchi
2023-09-08 15:20 ` [PATCH 2/2] gdb/doc: describe x87 registers Simon Marchi
2023-09-08 15:35 ` Eli Zaretskii
2023-09-08 17:03 ` Pedro Alves
2023-09-08 17:16 ` Simon Marchi
2023-09-08 15:37 ` [PATCH 1/2] gdb/doc: rename "x86 Architecture-specific Issues" section to "x86" Eli Zaretskii
2023-09-08 17:17 ` Simon Marchi [this message]
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=8e583748-66dc-49b4-b138-e197a68b2718@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@efficios.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.
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).