From: Michael Elizabeth Chastain <mec@shout.net>
To: jimb@redhat.com
Cc: bkoz@redhat.com, gdb-patches@sources.redhat.com, jingham@apple.com
Subject: Re: gdb.c++ testsuite 1: member data
Date: Tue, 14 May 2002 17:14:00 -0000 [thread overview]
Message-ID: <200205150014.g4F0Em520756@duracef.shout.net> (raw)
Jim Blandy asks:
> So, does Benjamin have approval to commit these tests?
No, not yet.
> Or will you add the kfails and commit the tests yourself?
That's quite likely, as I don't expect Benjamin K to be familiar
with the process of filing bug reports.
Michael C
next reply other threads:[~2002-05-15 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-14 17:14 Michael Elizabeth Chastain [this message]
2002-05-15 1:44 ` Benjamin Kosnik
-- strict thread matches above, loose matches on Subject: below --
2002-05-14 12:29 Michael Elizabeth Chastain
2002-05-14 14:27 ` Jim Blandy
2002-05-14 12:14 Benjamin Kosnik
2002-05-14 14:34 ` Daniel Jacobowitz
2002-05-14 18:56 ` Andrew Cagney
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=200205150014.g4F0Em520756@duracef.shout.net \
--to=mec@shout.net \
--cc=bkoz@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@redhat.com \
--cc=jingham@apple.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