Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: vladimir@codesourcery.com, gdb-patches@sources.redhat.com
Subject: Re: RFA: Remove gdb-events
Date: Mon, 14 Jul 2008 20:33:00 -0000	[thread overview]
Message-ID: <m3zlok5hpr.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080714171004.GC3998@adacore.com> (Joel Brobecker's message of "Mon\, 14 Jul 2008 10\:10\:04 -0700")

>>>>> "Joel" == Joel Brobecker <brobecker@adacore.com> writes:

Joel> My thought on this is that the observers should be installed
Joel> permanently and should have a way of determining whether the
Joel> current interpreter is the one they have been installed for
Joel> before doing anything else.

Ok.  Either way is fine by me -- I'll implement whatever Vladimir says.

Joel> The gdbtk team will probably be grateful that you took a look at their
Joel> code, but it's actually maintained by a different group, with a different
Joel> discussion list. I took a look, and the changes certainly look reasonable.
Joel> Let's send them a copy of the gdbtk patch (insight@sourceware.org) when
Joel> we're happy about the changes in GDB.

I sent a note and Keith replied, saying that this patch is ok.

Joel> Let's isolate the Makefile.in changes related to gdbtk and send them
Joel> to the insight list together with your other gdbtk changes.

So -- you would want this patch separated into two commits?
I am happy to do that, but it seems weird.  Logically it is a single
change.

I will address your other comments and submit an updated patch once I
hear back from Vladimir and, possibly, the TUI maintainer.

thanks,
Tom


  reply	other threads:[~2008-07-14 20:33 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-13  0:16 Tom Tromey
2008-07-13  3:26 ` Stan Shebs
2008-07-13 21:56   ` Tom Tromey
2008-08-01 16:20     ` Tom Tromey
2008-08-01 16:33       ` Subdir ChangeLogs (was Re: RFA: Remove gdb-events) Stan Shebs
2008-08-01 17:10         ` Subdir ChangeLogs Tom Tromey
2008-08-01 17:27           ` Stan Shebs
2008-08-01 17:54             ` Tom Tromey
2008-08-01 18:44             ` Eli Zaretskii
2008-08-01 18:55               ` Tom Tromey
2008-08-01 19:25                 ` Eli Zaretskii
2008-08-01 19:33                   ` Tom Tromey
2008-08-01 20:11                     ` Thiago Jung Bauermann
2008-08-02  7:13                     ` Eli Zaretskii
2008-08-02 16:52                       ` Tom Tromey
2008-08-02 17:28                         ` Eli Zaretskii
2008-08-02 20:24                         ` Thiago Jung Bauermann
2008-08-03  0:02           ` Michael Snyder
2008-08-01 17:40       ` RFA: Remove gdb-events Mark Kettenis
2008-07-14 17:10 ` Joel Brobecker
2008-07-14 20:33   ` Tom Tromey [this message]
2008-07-15  6:54     ` Joel Brobecker
2008-07-17 23:41   ` Tom Tromey
2008-07-21 16:54     ` GDB/MI PING (was: "Re: RFA: Remove gdb-events") Joel Brobecker
2008-07-22  0:56     ` RFA: Remove gdb-events Tom Tromey
2008-07-25 16:11       ` Tom Tromey
2008-07-20 11:46 ` Eli Zaretskii
2008-07-21 17:13 ` Vladimir Prus
2008-07-22  0:32   ` 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=m3zlok5hpr.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=vladimir@codesourcery.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