From: Joel Brobecker <brobecker@adacore.com>
To: S?rgio Durigan J?nior <sergiosdj@gmail.com>
Cc: gdb-patches@sourceware.org,
Thiago Jung Bauermann <bauerman@br.ibm.com>,
Luis Machado <luisgpm@linux.vnet.ibm.com>,
Matt Tyrlik <tyrlik@us.ibm.com>
Subject: Re: [PATCH 0/2] Support the new PPC476 processor
Date: Sun, 20 Dec 2009 18:24:00 -0000 [thread overview]
Message-ID: <20091220182356.GK2788@adacore.com> (raw)
In-Reply-To: <eebf789d0912200709w4fe10364s70a5894f2ee85708@mail.gmail.com>
> I am sorry about that. When I sent the patch, I decided to use the
> same approach that I used for the catch syscall series, but apparently
> it wasn't a good idea.
Not to worry. This is probably a matter of personal taste too, which
is why I did not demand, but rather ask if it was possible. In particular,
if someone else manages to review these patches, I'm prefectly happy.
> When I decided to use this term, I based that decision on the fact
> that gdbserver uses the same nomenclature: for example, it has a
> variable called `debug_hw_points', the methods `insert_point' and
> `remove_point', etc.
A very valid ... point! :-). If this is an already established
nomenclature, then this is fine. I don't see the point of changing now.
--
Joel
next prev parent reply other threads:[~2009-12-20 18:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 20:48 Sérgio Durigan Júnior
2009-12-17 4:42 ` Joel Brobecker
2009-12-17 14:19 ` Thiago Jung Bauermann
2009-12-17 16:15 ` Sérgio Durigan Júnior
2009-12-18 10:19 ` Eli Zaretskii
2009-12-20 12:33 ` Joel Brobecker
2009-12-30 3:13 ` Thiago Jung Bauermann
2009-12-30 20:43 ` Eli Zaretskii
2009-12-30 22:15 ` Daniel Jacobowitz
2009-12-31 4:05 ` Eli Zaretskii
2009-12-31 16:28 ` Daniel Jacobowitz
2009-12-31 16:50 ` Pedro Alves
2009-12-20 13:16 ` Joel Brobecker
2009-12-20 15:09 ` Sérgio Durigan Júnior
2009-12-20 18:24 ` Joel Brobecker [this message]
2009-12-21 12:54 ` Thiago Jung Bauermann
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=20091220182356.GK2788@adacore.com \
--to=brobecker@adacore.com \
--cc=bauerman@br.ibm.com \
--cc=gdb-patches@sourceware.org \
--cc=luisgpm@linux.vnet.ibm.com \
--cc=sergiosdj@gmail.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