From: Tom Tromey <tromey@redhat.com>
To: sami wagiaalla <swagiaal@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Defer symbol addition until construction is complete
Date: Mon, 09 Aug 2010 19:55:00 -0000 [thread overview]
Message-ID: <m3iq3jh885.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4C604B22.4060904@redhat.com> (sami wagiaalla's message of "Mon, 09 Aug 2010 14:38:26 -0400")
>>>>> "Sami" == sami wagiaalla <swagiaal@redhat.com> writes:
Sami> I am reposting since the rebase want trivial; I change the template
Sami> symbol code to take advantage of this clean up.
Sami> Is this cool ?
Yes, thanks.
Tom
next prev parent reply other threads:[~2010-08-09 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 15:28 sami wagiaalla
2010-07-29 20:58 ` Tom Tromey
2010-08-09 18:38 ` sami wagiaalla
2010-08-09 19:55 ` Tom Tromey [this message]
2010-08-10 7:44 ` Regression gdb.cp/temargs.exp: test value of P in inner_m [Re: [patch] Defer symbol addition until construction is complete] Jan Kratochvil
2010-08-10 14:34 ` sami wagiaalla
2010-08-20 20:21 ` sami wagiaalla
2010-08-20 21:54 ` Tom Tromey
2010-08-31 15:18 ` sami wagiaalla
2010-08-31 18:37 ` Tom Tromey
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=m3iq3jh885.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=swagiaal@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).