From: Pedro Franco de Carvalho <pedromfc@linux.ibm.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, uweigand@de.ibm.com
Subject: Re: [PATCH] [PowerPC] Document requirements for VSX feature
Date: Thu, 08 Nov 2018 13:28:00 -0000 [thread overview]
Message-ID: <87k1lnvgug.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <83y3a3bt7e.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> The only change is the last sentence, right?
I did also change "vector registers" to "vector-scalar registers" which
is the proper name for them. Sorry for the confusing diff, I
auto-formatted the paragraph.
> The change is okay, but please include the name of the node in the
> ChangeLog entry (in parentheses, as if it were the name of a
> function).
Ok! I'll change it to "* gdb.texinfo (PowerPC Features):"
> Thanks.
Thank you!
next prev parent reply other threads:[~2018-11-08 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-08 13:11 Pedro Franco de Carvalho
2018-11-08 13:23 ` Eli Zaretskii
2018-11-08 13:28 ` Pedro Franco de Carvalho [this message]
2018-11-09 18:12 ` Pedro Franco de Carvalho
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=87k1lnvgug.fsf@linux.vnet.ibm.com \
--to=pedromfc@linux.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=uweigand@de.ibm.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