From: Tom Tromey <tromey@redhat.com>
To: Sanimir Agovic <sanimir.agovic@intel.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] pass v2 instead of base_type to value_type.
Date: Thu, 29 Aug 2013 14:21:00 -0000 [thread overview]
Message-ID: <87eh9cshlf.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1377785588-13708-1-git-send-email-sanimir.agovic@intel.com> (Sanimir Agovic's message of "Thu, 29 Aug 2013 16:13:08 +0200")
>>>>> "Sanimir" == Sanimir Agovic <sanimir.agovic@intel.com> writes:
Sanimir> * valops.c (do_search_struct_field): Pass v2 instead of base_type to
Sanimir> value_type.
Ok.
Really this could go in under the obvious rule.
Tom
next prev parent reply other threads:[~2013-08-29 14:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 14:13 Sanimir Agovic
2013-08-29 14:21 ` Tom Tromey [this message]
2013-08-29 14:27 ` Agovic, Sanimir
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=87eh9cshlf.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sanimir.agovic@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