Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: asmundak@google.com, gdb-patches@sourceware.org
Subject: Re: RFC: Python gdb.Type method returning optimized out gdb.Value
Date: Tue, 14 Apr 2015 02:43:00 -0000	[thread overview]
Message-ID: <838udvctvj.fsf@gnu.org> (raw)
In-Reply-To: <21804.22480.660123.561679@ruffy2.mtv.corp.google.com>

> From: Doug Evans <dje@google.com>
> Date: Mon, 13 Apr 2015 16:57:04 -0700
> Cc: Alexander Smundak <asmundak@google.com>,
>     gdb-patches <gdb-patches@sourceware.org>
> 
> Doug Evans writes:
>  > On Tue, Apr 7, 2015 at 2:23 PM, Alexander Smundak <asmundak@google.com> wrote:
>  > > Thank you for the quick review.
>  > > Edited NEWS, renamed `create_optimized_out' to `optimized_out',
>  > > elided 'unavailable' from description, added blank line.
>  > > PTAL.
>  > >
>  > > gdb/doc/ChangeLog:
>  > >
>  > > 2015-04-07  Sasha Smundak  <asmundak@google.com>
>  > >
>  > >     * python.texi: New method documented.
>  > >
>  > > gdb/ChangeLog:
>  > >
>  > > 2015-04-07  Sasha Smundak  <asmundak@google.com>
>  > >
>  > >     * NEWS: Mention gdb.Type.optimized_out method.
>  > >     * python/py-type.c (typy_optimized_out):  New function.
>  > >
>  > > gdb/testsuite/ChangeLog:
>  > >
>  > > 2015-04-07  Sasha Smundak  <asmundak@google.com>
>  > >
>  > >     * gdb.python/py-type.exp: New test.
> 
> Hi.
> Just need a doc approval.

You've got it.


  reply	other threads:[~2015-04-14  2:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-03 20:33 Alexander Smundak
2015-04-07 17:44 ` Doug Evans
2015-04-07 21:23   ` Alexander Smundak
2015-04-12 16:48     ` Doug Evans
2015-04-13 23:57       ` Doug Evans
2015-04-14  2:43         ` Eli Zaretskii [this message]
2015-04-29  5:20     ` 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=838udvctvj.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=asmundak@google.com \
    --cc=dje@google.com \
    --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