From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Thiago Jung Bauermann <bauerman@br.ibm.com>,
gdb-patches@sourceware.org, luisgpm@linux.vnet.ibm.com,
tyrlik@us.ibm.com
Subject: Re: [PATCH 0/4] Support the BookE hardware debug features
Date: Thu, 24 Dec 2009 10:11:00 -0000 [thread overview]
Message-ID: <20091224101041.GX2788@adacore.com> (raw)
In-Reply-To: <83iqbx57r4.fsf@gnu.org>
> What's the decision regarding the new *-range commands? I see they
> are still being introduced. We have 1 voice against that and one in
> favor. If you are not convinced by what I wrote against them, I'd
> like to hear more opinions before we decide.
Just in case you are referring to my answer as in favor, I should
say that I'm more like 50-50, or only slightly in favor. I am not
against the syntax you suggested provided that it does not complicate
the implementation too much.
--
Joel
prev parent reply other threads:[~2009-12-24 10:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 0:31 Thiago Jung Bauermann
2009-12-24 4:12 ` Eli Zaretskii
2009-12-24 10:11 ` Joel Brobecker [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=20091224101041.GX2788@adacore.com \
--to=brobecker@adacore.com \
--cc=bauerman@br.ibm.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.com \
--cc=tyrlik@us.ibm.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