From: Pedro Alves <palves@redhat.com>
To: Muhammad Bilal <mbilal@codesourcery.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [patch] fix for checking the command ambiguousness.
Date: Tue, 17 Sep 2013 16:31:00 -0000 [thread overview]
Message-ID: <523883F4.5070207@redhat.com> (raw)
In-Reply-To: <5238833A.9080902@codesourcery.com>
As the test uses Python stuff to expose the bug, I'd appreciate
it if a Python person took a look.
Is this only triggerable with Python? If so, why?
--
Pedro Alves
next prev parent reply other threads:[~2013-09-17 16:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 9:22 Muhammad Bilal
2013-08-27 18:10 ` Pedro Alves
2013-08-28 8:16 ` Muhammad Bilal
[not found] ` <521DE287.2010208@redhat.com>
2013-08-28 14:17 ` Muhammad Bilal
2013-09-04 12:34 ` Muhammad Bilal
2013-09-10 10:33 ` Muhammad Bilal
2013-09-17 16:28 ` Muhammad Bilal
2013-09-17 16:31 ` Pedro Alves [this message]
2013-11-07 15:04 ` Tom Tromey
2013-11-07 14:53 ` 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=523883F4.5070207@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=mbilal@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