From: Tom Tromey <tromey@redhat.com>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Another annotation for threads
Date: Fri, 06 Jun 2008 02:44:00 -0000 [thread overview]
Message-ID: <m3abhzb7uf.fsf@fleche.redhat.com> (raw)
In-Reply-To: <20080606022958.GA23233@caradoc.them.org> (Daniel Jacobowitz's message of "Thu\, 5 Jun 2008 22\:29\:58 -0400")
>>>>> "Daniel" == Daniel Jacobowitz <drow@false.org> writes:
Daniel> On Thu, Jun 05, 2008 at 07:06:16PM -0600, Tom Tromey wrote:
>> Is this how things "ought" to work? I mean ideally?
Daniel> Yes. But there was disagreement over when a particular observer
Daniel> ought to be called.
I think I missed an earlier thread about this.
This disagreement could be solved, somewhat hackily, by adding more
information to the observer notification, so observers can more easily
discard the ones they are not interested in.
Anyway, thanks for responding. I don't want to talk about it too much
in the abstract -- but I did want to get a general idea for changes we
write on the Python branch, and I think I understand now.
Tom
next prev parent reply other threads:[~2008-06-06 2:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 6:13 Nick Roberts
2008-05-21 8:54 ` Eli Zaretskii
2008-06-05 19:30 ` Daniel Jacobowitz
2008-06-05 21:20 ` Nick Roberts
2008-06-05 21:26 ` Daniel Jacobowitz
2008-06-05 22:02 ` Joel Brobecker
2008-06-06 1:03 ` Nick Roberts
2008-06-06 6:59 ` Joel Brobecker
2008-06-06 0:50 ` Nick Roberts
2008-06-06 1:06 ` Tom Tromey
2008-06-06 2:30 ` Daniel Jacobowitz
2008-06-06 2:44 ` Tom Tromey [this message]
2008-06-06 2:39 ` Pedro Alves
2008-06-06 3:00 ` Nick Roberts
2008-06-06 11:44 ` Daniel Jacobowitz
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=m3abhzb7uf.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--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