From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: Re: [commit] make step_1 use step_once
Date: Thu, 11 Dec 2008 20:39:00 -0000 [thread overview]
Message-ID: <200812112038.33124.pedro@codesourcery.com> (raw)
In-Reply-To: <200812112035.27148.pedro@codesourcery.com>
On Thursday 11 December 2008 20:35:26, Pedro Alves wrote:
> Hi guys,
>
> This makes step_1 use step_once in the sync case as well to reduce
> code (and logic) duplication.
>
> I found out when moving patches between trees here that I was doing
> essentially what Daniel had already done in his pending inline frame
> support patch set, so I split and merged both. Any new bug is
> of course credited to yours truly. Daniel, I hope you don't mind me
> doing this.
>
Argh, the ChangeLog entry I commited was this one, not what in the patch:
2008-12-11 Daniel Jacobowitz <dan@codesourcery.com>
Pedro Alves <pedro@codesourcery.com>
* infcmd.c (step_1): Use step_once in the synchronous case too.
(step_1_continuation): Wrap line.
(step_once): Adjust comment. Only install the continuation in
async mode.
> Tested on x86-64-unknown-linux-gnu sync/async, and checked in.
>
--
Pedro Alves
prev parent reply other threads:[~2008-12-11 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 20:36 Pedro Alves
2008-12-11 20:39 ` Pedro Alves [this message]
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=200812112038.33124.pedro@codesourcery.com \
--to=pedro@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