From: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: committed: [PATCH] Remove redundant condition checking.
Date: Wed, 16 Jan 2013 14:47:00 -0000 [thread overview]
Message-ID: <50F6BD48.40909@codesourcery.com> (raw)
In-Reply-To: <50F5C7E9.9010207@redhat.com>
On 01/16/2013 05:19 AM, Pedro Alves wrote:
>> '(lwp->bp_reinsert != 0'.
> ^
>
> That '(' is spurious though.
The spurious '(' is removed and patch is committed.
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-01-16 14:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 9:35 Yao Qi
2013-01-15 21:19 ` Pedro Alves
2013-01-15 21:20 ` Pedro Alves
2013-01-16 14:47 ` Yao Qi [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-01-15 9:31 Yao Qi
2013-01-15 14:38 ` Pedro Alves
2013-01-16 14:48 ` committed: " Yao Qi
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=50F6BD48.40909@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
/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