From: Gabriel Dos Reis <gdr@cs.tamu.edu>
To: Daniel Jacobowitz <dan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: PATCH to gdb/linux-nat.c
Date: Fri, 09 Feb 2007 19:44:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.58.0702091343530.11220@sun> (raw)
In-Reply-To: <20070209194127.GA31603@nevyn.them.org>
On Fri, 9 Feb 2007, Daniel Jacobowitz wrote:
| On Fri, Feb 09, 2007 at 01:39:50PM -0600, Gabriel Dos Reis wrote:
| > One more favor: Would you mind looking at my other patch? The GCC PR
| > I filled was demonstrated to be a duplicate and nothing happened
| > since the first PR was filled; I believe GDB+GCC-4.2.0 is affected too. I
| > think the patch I sent works around the problem within GDB and
| > "improves" the const-correctness of the two functions involved.
|
| I'd prefer to wait a little while to see if anyone else (Joel maybe)
| has comments on that one - he's the expert on that code.
Thanks makes sense. Thanks!
-- Gaby
next prev parent reply other threads:[~2007-02-09 19:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 9:08 Gabriel Dos Reis
2007-02-09 13:49 ` Daniel Jacobowitz
2007-02-09 16:38 ` Gabriel Dos Reis
2007-02-09 19:24 ` Daniel Jacobowitz
2007-02-09 19:39 ` Gabriel Dos Reis
2007-02-09 19:41 ` Daniel Jacobowitz
2007-02-09 19:44 ` Gabriel Dos Reis [this message]
2007-02-09 20:00 ` Joel Brobecker
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=Pine.GSO.4.58.0702091343530.11220@sun \
--to=gdr@cs.tamu.edu \
--cc=dan@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