From: Tom Tromey <tromey@redhat.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: markus.t.metzger@intel.com, gdb-patches@sourceware.org,
markus.t.metzger@gmail.com, palves@redhat.com
Subject: Re: [PATCH 1/1] gdb, python: update threads in Inferior.threads ()
Date: Wed, 25 Jul 2012 16:16:00 -0000 [thread overview]
Message-ID: <874novkeam.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20120719184050.GA15108@host2.jankratochvil.net> (Jan Kratochvil's message of "Thu, 19 Jul 2012 20:40:50 +0200")
>>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
Jan> OK with the issue below but please check it in only after several
Jan> days, there is questionable the caching of threads list.
I think making thread notification smarter, as you mention upthread,
would be good, but isn't needed for this patch. This patch is an
improvement on its own.
Tom
next prev parent reply other threads:[~2012-07-25 16:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 15:30 markus.t.metzger
2012-07-19 18:41 ` Jan Kratochvil
[not found] ` <2832024D-3061-4A13-BBF5-656C504C295D@gmail.com>
2012-07-24 8:08 ` Metzger, Markus T
2012-07-25 16:13 ` Tom Tromey
2012-07-26 5:51 ` Metzger, Markus T
2012-07-25 16:16 ` Tom Tromey [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-26 12:20 markus.t.metzger
2012-07-25 8:27 markus.t.metzger
2012-07-25 16:15 ` Tom Tromey
2012-07-26 7:51 ` Metzger, Markus T
2012-07-26 8:43 ` Jan Kratochvil
2012-07-26 8:49 ` Metzger, Markus T
2012-07-24 8:12 markus.t.metzger
2012-07-24 14:36 ` Phil Muldoon
2012-07-06 9:50 markus.t.metzger
2012-07-06 18:12 ` Tom Tromey
2012-07-19 15:27 ` Metzger, Markus T
2012-07-18 13:54 ` Jan Kratochvil
2012-07-19 15:27 ` Metzger, Markus T
2012-07-19 18:45 ` Jan Kratochvil
2012-07-20 7:57 ` Metzger, Markus T
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=874novkeam.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=markus.t.metzger@gmail.com \
--cc=markus.t.metzger@intel.com \
--cc=palves@redhat.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