From: Doug Evans <dje@google.com>
To: Justin Lebar <jlebar@google.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
Joel Brobecker <brobecker@adacore.com>,
gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2] Fix documentation for Type.template_argument.
Date: Tue, 02 Sep 2014 22:24:00 -0000 [thread overview]
Message-ID: <CADPb22QhOYDxhhL3Ep4F+Qj2V1dqR5aX2ivUzr8JG2o6Zo96Vg@mail.gmail.com> (raw)
In-Reply-To: <CAMuNMfp79fC-kcY6rix2LO8Yw0yKnzzyFK94GyqoWgwg8_UYgg@mail.gmail.com>
Yeah, it's good to go.
On Tue, Sep 2, 2014 at 3:13 PM, Justin Lebar <jlebar@google.com> wrote:
> Can we finally submit this patch, or is there something else I need to do here?
>
> On Sun, Aug 17, 2014 at 11:25 AM, Doug Evans <dje@google.com> wrote:
>> On Mon, Jul 7, 2014 at 10:43 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>>>> From: Justin Lebar <jlebar@google.com>
>>>> Date: Mon, 7 Jul 2014 10:28:58 -0700
>>>> Cc: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
>>>>
>>>> > Otherwise, the patch is OK Texinfo-wise; I don't know enough about
>>>> > these issues to tell whether the content is correct
>>>>
>>>> I thought this indicated I should wait for someone else to chime in?
>>>
>>> You understood correctly. Since you are correcting existing
>>> documentation, I think it would be good if someone who knows that
>>> stuff looked at the corrections from the contents point of view and
>>> approved them.
>>>
>>> Thanks.
>>
>> Content-wise, the patch is ok with me.
next prev parent reply other threads:[~2014-09-02 22:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-24 22:38 Justin Lebar
2014-07-06 17:57 ` Justin Lebar
2014-07-07 14:42 ` Joel Brobecker
2014-07-07 15:32 ` Eli Zaretskii
2014-07-07 17:29 ` Justin Lebar
2014-07-07 17:44 ` Eli Zaretskii
2014-08-17 18:25 ` Doug Evans
2014-09-02 22:13 ` Justin Lebar
2014-09-02 22:24 ` Doug Evans [this message]
2014-09-03 23:44 ` Doug Evans
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=CADPb22QhOYDxhhL3Ep4F+Qj2V1dqR5aX2ivUzr8JG2o6Zo96Vg@mail.gmail.com \
--to=dje@google.com \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=jlebar@google.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