From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com, jason@redhat.com
Subject: Re: PATCH to gdb.c++/*
Date: Thu, 10 Jan 2002 11:41:00 -0000 [thread overview]
Message-ID: <200201101941.NAA04335@duracef.shout.net> (raw)
This patch is approved.
Michael C
===
2002-01-10 Jason Merrill <jason@redhat.com>
* gdb.c++/namespace.exp: Accept trailing const for 'this'.
* gdb.c++/classes.exp: Accept 'A const' or 'const A' in copy
constructors.
* gdb.c++/derivation.exp: Likewise.
* gdb.c++/templates.exp: Likewise.
* gdb.c++/virtfunc.exp: Likewise.
next reply other threads:[~2002-01-10 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-10 11:41 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-01-10 11:25 Jason Merrill
2002-01-10 11:54 ` 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=200201101941.NAA04335@duracef.shout.net \
--to=mec@shout.net \
--cc=gdb-patches@sources.redhat.com \
--cc=jason@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