From: Stan Shebs <shebs@cygnus.com>
To: guo@cup.hp.com
Cc: cagney@cygnus.com, gdb@sourceware.cygnus.com
Subject: Re: Testsuite Organization Proposal
Date: Thu, 24 Jun 1999 15:29:00 -0000 [thread overview]
Message-ID: <199906242229.PAA25845@andros.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9906241459090.3461-100000@hpcll168.cup.hp.com>
Date: Thu, 24 Jun 1999 15:02:04 -0700 (PDT)
From: Jimmy Guo <guo@cup.hp.com>
How about moving the C++ part of smoke.exp and smoke.cc to gdb.c++?
I'm about to provide a patch for the gdb.base suite as the part of the
test suite merge effort between HP's tree and Cygnus tree, with
assistance from Stan. This could be a time we split up smoke.exp.
Does anybody at HP or elsewhere use this file as a smoke test? I'm
pretty sure nobody at Cygnus does. The tests are generally redundant,
so you're losing much test coverage by dropping it. If it really is
useful, then splitting up is OK too.
Stan
next prev parent reply other threads:[~1999-06-24 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199906242141.OAA25771@andros.cygnus.com>
1999-06-24 15:02 ` Jimmy Guo
1999-06-24 15:29 ` Stan Shebs [this message]
1999-06-24 17:12 ` Jimmy Guo
[not found] <199906142351.QAA06182@andros.cygnus.com>
1999-06-14 17:03 ` Todd Whitesel
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=199906242229.PAA25845@andros.cygnus.com \
--to=shebs@cygnus.com \
--cc=cagney@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=guo@cup.hp.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