From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: Yao Qi <yao@codesourcery.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Move VEC (const_char_ptr) to gdb_vecs.h
Date: Fri, 20 Apr 2012 18:05:00 -0000 [thread overview]
Message-ID: <m3r4viz6fx.fsf@redhat.com> (raw)
In-Reply-To: <87ty0ejvy5.fsf@fleche.redhat.com> (Tom Tromey's message of "Fri, 20 Apr 2012 08:53:54 -0600")
On Friday, April 20 2012, Tom Tromey wrote:
>>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
>
> Yao> On 04/20/2012 12:23 PM, Sergio Durigan Junior wrote:
>>> This patch moves the definition of VEC (const_char_ptr) to gdb_vecs.h.
>>> It is rather obvious, but I decided to ask either way. Ok to apply?
>
> Yao> It is right to me, but I am not the people to approve it. IIRC,
> Yao> gdb_vecs.h is created to put several DEF_VEC_P in it.
>
> Yeah.
>
> The patch is ok.
Thanks, committed.
http://sourceware.org/ml/gdb-cvs/2012-04/msg00165.html
--
Sergio
prev parent reply other threads:[~2012-04-20 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 4:26 Sergio Durigan Junior
2012-04-20 4:58 ` Sergio Durigan Junior
2012-04-20 7:21 ` Yao Qi
2012-04-20 15:02 ` Tom Tromey
2012-04-20 18:05 ` Sergio Durigan Junior [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=m3r4viz6fx.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
--cc=yao@codesourcery.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