From: Joel Brobecker <brobecker@gnat.com>
To: gdb@sources.redhat.com
Subject: Re: Need suggestions on how to test observer.c
Date: Tue, 11 Mar 2003 19:09:00 -0000 [thread overview]
Message-ID: <20030311190941.GG953@gnat.com> (raw)
In-Reply-To: <20030310232601.GA13541@nevyn.them.org>
> I have no objection to adding these dummies to observer.c; I think I
> prefer that, because it tests observer code in the closer to the same
> way it will be used.
That makes good sense. I'll way for a few more day (say until the end of
this week), and then take this approach if nobody objects.
Thanks Daniel!
--
Joel
next prev parent reply other threads:[~2003-03-11 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-10 22:43 Joel Brobecker
2003-03-10 23:26 ` Daniel Jacobowitz
2003-03-11 19:09 ` Joel Brobecker [this message]
2003-03-11 20:31 ` David Carlton
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=20030311190941.GG953@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb@sources.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