From: Eli Zaretskii <eliz@gnu.org>
To: Hui Zhu <hui_zhu@mentor.com>
Cc: gdb-patches@sourceware.org, Yao_Qi@mentor.com, stan_shebs@mentor.com
Subject: Re: [PATCH] Autoload-breakpoints without report-async
Date: Thu, 03 May 2012 17:03:00 -0000 [thread overview]
Message-ID: <83ipgd6vw0.fsf@gnu.org> (raw)
In-Reply-To: <4FA2B434.60706@mentor.com>
> Date: Fri, 4 May 2012 00:37:08 +0800
> From: Hui Zhu <hui_zhu@mentor.com>
> CC: Yao Qi <Yao_Qi@mentor.com>, Stan Shebs <stan_shebs@mentor.com>, Eli
> Zaretskii <eliz@gnu.org>
>
> According to the mail form Yao. I thought make the autoload-breakpoints and report-async function together make it too hard to review. So I move the function that depend on the report-async to be a series of separate patches after report-async.
> Then the other patches of autoload-breakpoints can be reveiw separate from report-async.
Is the documentation part here any different from the last time I
reviewed it?
next prev parent reply other threads:[~2012-05-03 17:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 16:37 Hui Zhu
2012-05-03 17:03 ` Eli Zaretskii [this message]
2012-05-04 1:00 ` Hui Zhu
2012-05-04 7:02 ` Eli Zaretskii
2012-05-06 1:53 ` Hui Zhu
2012-05-07 19:40 ` Eli Zaretskii
2012-05-15 11:29 ` Hui Zhu
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=83ipgd6vw0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=Yao_Qi@mentor.com \
--cc=gdb-patches@sourceware.org \
--cc=hui_zhu@mentor.com \
--cc=stan_shebs@mentor.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