From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: walfred.tedeschi@intel.com, joseph@codesourcery.com,
gdb-patches@sourceware.org
Subject: Re: [OBV PATCH] MPX documentation
Date: Mon, 11 Jan 2016 15:41:00 -0000 [thread overview]
Message-ID: <83r3hoktsf.fsf@gnu.org> (raw)
In-Reply-To: <56939524.50406@redhat.com> (message from Pedro Alves on Mon, 11 Jan 2016 11:42:28 +0000)
> Date: Mon, 11 Jan 2016 11:42:28 +0000
> From: Pedro Alves <palves@redhat.com>
> CC: walfred.tedeschi@intel.com, joseph@codesourcery.com,
> gdb-patches@sourceware.org
>
> On 12/21/2015 03:39 PM, Eli Zaretskii wrote:
> >> Date: Mon, 21 Dec 2015 13:47:56 +0000
> >> From: Pedro Alves <palves@redhat.com>
> >> CC: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
> >>
> >>> From: Joseph Myers [mailto:joseph@codesourcery.com]
> >>> On Thu, 17 Dec 2015, Eli Zaretskii wrote:
> >>>>> From: Walfred Tedeschi <walfred.tedeschi@intel.com>
> >>>>> Fix some trademarks on MPX section.
> >>>>
> >>>> Do we have to?
> >>>
> >>> The GNU Coding Standards say "Please do not include any trademark acknowledgements in GNU software packages or documentation.". So the patch is wrong.
> >>
> >> Does that mean that all existing "(R)" occurrences in the documentation
> >> should be removed?
> >
> > I guess so, yes.
>
> Like so?
Yes, thanks.
prev parent reply other threads:[~2016-01-11 15:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 13:24 Walfred Tedeschi
2015-12-17 16:19 ` Eli Zaretskii
2015-12-17 18:05 ` Joseph Myers
2015-12-18 7:48 ` Tedeschi, Walfred
2015-12-21 13:48 ` Pedro Alves
2015-12-21 15:39 ` Eli Zaretskii
2015-12-21 17:38 ` Pedro Alves
2016-01-11 11:42 ` Pedro Alves
2016-01-11 12:35 ` Tedeschi, Walfred
2016-01-11 14:07 ` Pedro Alves
2016-01-11 15:41 ` Eli Zaretskii [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=83r3hoktsf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=joseph@codesourcery.com \
--cc=palves@redhat.com \
--cc=walfred.tedeschi@intel.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