From: Tom Tromey <tromey@redhat.com>
To: sami wagiaalla <swagiaal@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [patch] Overload resolution test case
Date: Wed, 06 Oct 2010 22:34:00 -0000 [thread overview]
Message-ID: <m31v832bog.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4CAC9648.2010006@redhat.com> (sami wagiaalla's message of "Wed, 06 Oct 2010 11:31:20 -0400")
>>>>> "Sami" == sami wagiaalla <swagiaal@redhat.com> writes:
Sami> Same patch with an additional test for sequence length. This takes
Sami> care of the FIXME in the previous patch.
This is ok. Thanks for doing this, I like this approach of writing the
tests first.
Tom
prev parent reply other threads:[~2010-10-06 22:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 19:06 sami wagiaalla
2010-10-06 15:31 ` sami wagiaalla
2010-10-06 22:34 ` Tom Tromey [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=m31v832bog.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).