From: Joel Brobecker <brobecker@adacore.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: fix PR 14386
Date: Wed, 15 Aug 2012 19:50:00 -0000 [thread overview]
Message-ID: <20120815194938.GA7873@adacore.com> (raw)
In-Reply-To: <87lihi60hu.fsf@fleche.redhat.com>
> Joel> If it is deemed extra safe, and useful, I don't see a problem.
> Joel> But I am fine either way.
>
> I think it is safe, but I think people other than me ought to say so.
Pedro said it seemed obvious even to him. I agree it seems correct
as well. I would put it in.
--
Joel
next prev parent reply other threads:[~2012-08-15 19:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-01 18:11 Tom Tromey
2012-08-01 19:29 ` Tom Tromey
2012-08-01 20:31 ` Pedro Alves
2012-08-06 9:42 ` Phil Muldoon
2012-08-06 18:43 ` Tom Tromey
2012-08-06 19:16 ` Tom Tromey
2012-08-13 18:17 ` Joel Brobecker
2012-08-13 19:44 ` Tom Tromey
2012-08-15 19:50 ` Joel Brobecker [this message]
2012-08-16 18:22 ` Tom Tromey
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=20120815194938.GA7873@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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