From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Remove board setting `gdb,cannot_call_functions'
Date: Mon, 23 Apr 2012 13:42:00 -0000 [thread overview]
Message-ID: <87d36yh8f2.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1335177254-5616-1-git-send-email-yao@codesourcery.com> (Yao Qi's message of "Mon, 23 Apr 2012 18:34:14 +0800")
>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
Yao> Some parts of patch shows that this setting is related
Yao> to 2416, but PR 2416 is not related to this at all,
Yao> Bug 2416 - autogen.sh, should take relative or absolute path, and configure
Yao> http://sourceware.org/bugzilla/show_bug.cgi?id=2416
When we moved from gnats to bugzilla, the PRs were all renumbered, but
we didn't fix the comments.
You can map from the old number to the new by adding 7105.
Or search for "Converted from Gnats NNN".
I get http://sourceware.org/bugzilla/show_bug.cgi?id=9521
But, this bug doesn't really seem related either.
So maybe it is a bug in the scripts :)
Tom
next prev parent reply other threads:[~2012-04-23 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-23 13:18 Yao Qi
2012-04-23 13:42 ` Tom Tromey [this message]
2012-04-24 14:13 ` Pedro Alves
2012-04-24 14:36 ` Yao Qi
2012-05-01 2:34 ` Jan Kratochvil
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=87d36yh8f2.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--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