From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Yao Qi <yao@codesourcery.com>
Subject: Re: Add comments on step_after_step_resume_breakpoint
Date: Wed, 07 Sep 2011 09:53:00 -0000 [thread overview]
Message-ID: <201109071045.57279.pedro@codesourcery.com> (raw)
In-Reply-To: <4E66C8ED.5070902@codesourcery.com>
On Wednesday 07 September 2011 02:29:17, Yao Qi wrote:
> When I am reading struct thread_info, I find the comment on
> step_after_step_resume_breakpoint is not helpful to me to understand it,
> until I read the original patch here
> http://cygwin.com/ml/gdb-patches/2004-08/msg00743.html
>
> The explanation of the patch was very clear, but it is missing in the
> comment of code. This patch is to copy some of words in original patch
> post to the comment on field `step_after_step_resume_breakpoint', in
> order to make comment self-explained.
>
> OK to apply?
Okay.
--
Pedro Alves
next prev parent reply other threads:[~2011-09-07 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 2:35 Yao Qi
2011-09-07 9:53 ` Pedro Alves [this message]
2011-09-07 13:58 ` [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=201109071045.57279.pedro@codesourcery.com \
--to=pedro@codesourcery.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