Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: "Sérgio Durigan Júnior" <sergiodj@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 0/3] catch syscall -- try 5 -- Introduction
Date: Thu, 23 Apr 2009 01:18:00 -0000	[thread overview]
Message-ID: <m3d4b4rwuj.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1240446781.2000.82.camel@miki> (=?utf-8?Q?=22S=C3=A9rgio?=  Durigan =?utf-8?Q?J=C3=BAnior=22's?= message of "Wed\, 22 Apr 2009  21\:33\:01 -0300")

>>>>> "Sérgio" == Sérgio Durigan Júnior <sergiodj@linux.vnet.ibm.com> writes:

Sérgio> There's one thing worth mentioning: this patch implements the
Sérgio> command "maint set data-directory", which is already
Sérgio> implemented by one of Tromey's pretty-printing patches. If
Sérgio> Tromey's patches are accepted first, then I can (need) modify
Sérgio> my patch in order to use his version of the command

I can push this particular one in any time.  If I remember, I'll do it
tomorrow -- or ping on me on irc.

It is really only the MI patch that is waiting.  I thought it would be
good for Vladimir to look at the new MI commands before I put it in.
I could actually put in all the earlier patches immediately; I will do
that barring objection.

Tom


  reply	other threads:[~2009-04-23  1:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23  0:33 Sérgio Durigan Júnior
2009-04-23  1:18 ` Tom Tromey [this message]
2009-04-23  2:29   ` Sérgio Durigan Júnior
2009-04-23 18:23     ` Tom Tromey
2009-04-23 21:27       ` Tom Tromey
2009-04-24 13:47         ` Eli Zaretskii
2009-04-23 11:49 ` Hui Zhu
2009-04-23 15:16   ` Sérgio Durigan Júnior
2009-04-23 15:28     ` Hui Zhu
2009-04-23 15:52       ` Sérgio Durigan Júnior
2009-05-07  3:22 ` Hui Zhu
2009-05-08  1:23   ` Sérgio Durigan Júnior
2009-05-29 20:34     ` Sérgio Durigan Júnior
2009-06-29  2:15       ` Hui Zhu
2009-06-29 15:30         ` Tom Tromey
2009-05-17 20:43 ` 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=m3d4b4rwuj.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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