From: Siva Chandra <sivachandra@google.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/4 v1] Add xmethod documentation and NEWS entry
Date: Mon, 02 Jun 2014 20:43:00 -0000 [thread overview]
Message-ID: <CAGyQ6gyw=8WRin3VFZkZdmYWQ=1MBGmdcmJenh595cGnHj7RpQ@mail.gmail.com> (raw)
In-Reply-To: <83ha439l4m.fsf@gnu.org>
On Mon, Jun 2, 2014 at 12:17 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Mon, 2 Jun 2014 12:06:12 -0700
>> From: Siva Chandra <sivachandra@google.com>
>>
>> The attached patch is almost the same as v19 except that it adds a
>> small note about the xmethod example mentioning that xmethod in the
>> example is slightly a different version of C++ operator+.
>
> Could you please identify the addition explicitly? I'm not sure which
> note did you have in mind.
Sorry for not being explicit. The part I am referring to is in the
node "Writing an Xmethod". It is in the "@noindent" piece right after
the first C++ example listing.
next prev parent reply other threads:[~2014-06-02 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 19:06 Siva Chandra
2014-06-02 19:17 ` Eli Zaretskii
2014-06-02 20:43 ` Siva Chandra [this message]
2014-06-03 6:57 ` Eli Zaretskii
2014-06-03 17:10 ` Siva Chandra
2014-06-03 17:57 ` Joel Brobecker
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='CAGyQ6gyw=8WRin3VFZkZdmYWQ=1MBGmdcmJenh595cGnHj7RpQ@mail.gmail.com' \
--to=sivachandra@google.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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