From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com
Subject: [patch] fnchange.lst: add testsuite/gdb.c++/pr-1210.{c,exp}
Date: Thu, 26 Jun 2003 18:38:00 -0000 [thread overview]
Message-ID: <200306261838.h5QIcRJg015104@duracef.shout.net> (raw)
This patch adds pr-1210.cc and pr-1210.exp to fnchange.lst.
I haven't tested this patch. I just wait for the nightly ARI run
and see if I got it right. :)
I'm committing this as an obvious fix to HEAD.
If this works okay in tonight's ARI tables, may I have permission
to commit it to gdb_6_0-branch as well?
Michael C
2003-06-26 Michael Chastain <mec@shout.net>
* config/djgpp/fnchange.lst: Add gdb/testsuite/gdb.c++/pr-1210.cc,
gdb/testsuite/gdb.c++/pr-1210.exp.
Index: config/djgpp/fnchange.lst
===================================================================
RCS file: /cvs/src/src/gdb/config/djgpp/fnchange.lst,v
retrieving revision 1.52
diff -u -r1.52 fnchange.lst
--- config/djgpp/fnchange.lst 26 Jun 2003 18:09:24 -0000 1.52
+++ config/djgpp/fnchange.lst 26 Jun 2003 18:34:33 -0000
@@ -251,6 +251,8 @@
@V@/gdb/testsuite/gdb.c++/ovldbreak.exp @V@/gdb/testsuite/gdb.cxx/ovldbreak.exp
@V@/gdb/testsuite/gdb.c++/pr-1023.cc @V@/gdb/testsuite/gdb.cxx/pr-1023.cc
@V@/gdb/testsuite/gdb.c++/pr-1023.exp @V@/gdb/testsuite/gdb.cxx/pr-1023.exp
+@V@/gdb/testsuite/gdb.c++/pr-1210.cc @V@/gdb/testsuite/gdb.cxx/pr-1210.cc
+@V@/gdb/testsuite/gdb.c++/pr-1210.exp @V@/gdb/testsuite/gdb.cxx/pr-1210.exp
@V@/gdb/testsuite/gdb.c++/pr-574.cc @V@/gdb/testsuite/gdb.cxx/pr-574.cc
@V@/gdb/testsuite/gdb.c++/pr-574.exp @V@/gdb/testsuite/gdb.cxx/pr-574.exp
@V@/gdb/testsuite/gdb.c++/printmethod.cc @V@/gdb/testsuite/gdb.cxx/printmethod.cc
next reply other threads:[~2003-06-26 18:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-26 18:38 Michael Elizabeth Chastain [this message]
2003-06-26 18:56 ` Daniel Jacobowitz
2003-06-26 19:34 ` Andrew Cagney
2003-06-27 17:42 ` Eli Zaretskii
2003-06-27 2:19 Michael Elizabeth Chastain
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=200306261838.h5QIcRJg015104@duracef.shout.net \
--to=mec@shout.net \
--cc=gdb-patches@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