From: Daniel Jacobowitz <drow@false.org>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: Pedro Alves <pedro@codesourcery.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] catch syscall -- try 4 -- Architecture-independent part
Date: Thu, 09 Apr 2009 19:36:00 -0000 [thread overview]
Message-ID: <20090409193556.GA27633@caradoc.them.org> (raw)
In-Reply-To: <1239305373.6452.13.camel@miki>
On Thu, Apr 09, 2009 at 04:29:33PM -0300, Sérgio Durigan Júnior wrote:
> So this is my opinion about this: I have the complete catch syscall
> patch here (the only thing that's missing is the MI support), so what do
> you think if we just push this patch upstream as-is (which is: in a
> pretty good shape, as far as I understood the others developers' --
> including yours -- comments), and postpone this MI support? I think I
> should be able to sit down and implement this support until the end of
> this semester, is it good for you?
Yes, that's fine. If someone else needs it, they'll fill it in.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-04-09 19:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 0:31 Sérgio Durigan Júnior
2009-01-26 0:51 ` Pedro Alves
2009-01-26 4:56 ` Sérgio Durigan Júnior
2009-01-26 17:04 ` Sérgio Durigan Júnior
2009-02-01 19:33 ` Daniel Jacobowitz
2009-02-25 21:44 ` Sérgio Durigan Júnior
2009-02-28 0:44 ` Daniel Jacobowitz
2009-03-08 18:16 ` Sérgio Durigan Júnior
2009-03-09 13:19 ` Daniel Jacobowitz
2009-03-09 14:09 ` Sérgio Durigan Júnior
2009-03-09 18:39 ` Pedro Alves
2009-03-09 18:56 ` Daniel Jacobowitz
2009-03-09 18:31 ` Pedro Alves
2009-03-29 21:16 ` Sérgio Durigan Júnior
2009-03-31 16:39 ` Daniel Jacobowitz
2009-04-09 19:29 ` Sérgio Durigan Júnior
2009-04-09 19:36 ` Daniel Jacobowitz [this message]
2009-04-09 20:21 ` Sérgio Durigan Júnior
2009-04-15 23:12 ` Sérgio Durigan Júnior
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=20090409193556.GA27633@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.com \
--cc=sergiodj@linux.vnet.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