From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: async patch (no. 4)
Date: Sun, 17 Jun 2007 15:21:00 -0000 [thread overview]
Message-ID: <20070617152125.GA17563@caradoc.them.org> (raw)
In-Reply-To: <18036.65200.916738.36790@kahikatea.snap.net.nz>
On Sun, Jun 17, 2007 at 09:28:16PM +1200, Nick Roberts wrote:
> I'm not sure if this was the last message in the thread but I'd like to
> see if we can get something committed after GDB 6.7 goes out.
Neither of us understands what parts of the patch do; in fact, I
understand almost none of it. I think it would be a very bad decision
for us to commit structural changes to GDB that we do not understand
(even if they are disabled by default), and I think we have no hope of
keeping the code working and improving it unless it is clearer. These
are the same requirements we apply to other changes.
I'd be happy to help you merge this, if you can break it down into
well-understood and necessary pieces. I can help with making the
native wait case asynchronous, since I know how that works. I also
have a patch lying around that makes target async-remote work a bit
better.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-06-17 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 7:05 Nick Roberts
2007-01-12 18:31 ` Daniel Jacobowitz
2007-01-12 22:24 ` Nick Roberts
2007-01-12 23:03 ` Daniel Jacobowitz
2007-06-17 9:28 ` Nick Roberts
2007-06-17 15:21 ` Daniel Jacobowitz [this message]
2007-06-17 20:50 ` Nick Roberts
2007-06-18 2:46 ` Daniel Jacobowitz
2007-06-18 5:00 ` Nick Roberts
2007-06-18 11:32 ` Daniel Jacobowitz
2007-06-18 21:48 ` Nick Roberts
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=20070617152125.GA17563@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=nickrob@snap.net.nz \
/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