From: Doug Evans <dje@google.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PR cli/13110
Date: Wed, 07 Sep 2011 17:42:00 -0000 [thread overview]
Message-ID: <CADPb22R4mmb5HPHc3Z6odpnF50dA337GUEgoXNquUBfAjHHS1w@mail.gmail.com> (raw)
In-Reply-To: <201109071512.01995.pedro@codesourcery.com>
On Wed, Sep 7, 2011 at 7:12 AM, Pedro Alves <pedro@codesourcery.com> wrote:
> How about removing the registers_changed calls once and
> for all?
Having/requiring them to be littered throughout the code always seemed
a tad fragile ...
next prev parent reply other threads:[~2011-09-07 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 16:50 Pedro Alves
2011-09-07 1:29 ` Doug Evans
2011-09-07 14:28 ` Pedro Alves
2011-09-07 17:42 ` Doug Evans [this message]
2011-09-14 13:40 ` Pedro Alves
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=CADPb22R4mmb5HPHc3Z6odpnF50dA337GUEgoXNquUBfAjHHS1w@mail.gmail.com \
--to=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@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