From: Daniel Jacobowitz <drow@mvista.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite] more tests in gdb.c++/m-static
Date: Fri, 16 Aug 2002 14:30:00 -0000 [thread overview]
Message-ID: <20020816213122.GA12044@nevyn.them.org> (raw)
In-Reply-To: <ro1fzxewlg8.fsf@jackfruit.Stanford.EDU>
On Fri, Aug 16, 2002 at 02:19:35PM -0700, David Carlton wrote:
> I've added some tests to gdb.c++/m-static that correspond to the patch
> in <http://sources.redhat.com/ml/gdb-patches/2002-08/msg00385.html>;
> patches below.
>
> A few tangential questions:
>
> * I hope I got the stuff in brackets in the subject correct; is rfa
> "request for approval"?
Yup. You might want to specify c++testsuite and/or CC the various
testsuite maintainers.
> * What's the convention for submitting new files (as opposed to
> patches to existing files)? (I'd look through the mail archive for
> examples, but I don't seem to be able to access it right now.) I'm
> attaching them below as files and hoping that the mailer will make
> it clear what they're named and so forth; please let me know if I
> should do anything else.
I usually use diff -N to do this.
> * CONTRIBUTE suggests using "cvs diff -cp", but everybody submits
> unidiff patches. Should I change it to say "cvs diff -up"?
Either works. I like unidiff, personally.
> * Does "make clean" actually clean up the testsuite directory
> properly? Looking at the Makefile in gdb.c++, it seems like it
> cleans up whatever's in the EXECUTABLES variable, which certainly
> doesn't include all the executables in that directory. Is there
> something else magic going on, or should I audit the Makefile.in's
> in the various directories to see if they clean up everything?
> (Yes, I know, I should really type "make clean" and see what it
> does, but I don't feel like rebuilding gdb if somebody can answer
> the question quickly.)
No, the testsuite directory doesn't get cleaned properly. I recommend
using a separate object directory anyway; it keeps things neater.
Oh, and you might want to use namespace names that aren't in the
implementation space (__gnu is in the implementation space, because it
starts with two underscores. _[A-Z] is also reserved.)
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-08-16 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 14:19 David Carlton
2002-08-16 14:30 ` Daniel Jacobowitz [this message]
2002-08-16 14:37 ` David Carlton
2002-08-22 10:09 ` David Carlton
2002-08-22 10:23 ` 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=20020816213122.GA12044@nevyn.them.org \
--to=drow@mvista.com \
--cc=carlton@math.stanford.edu \
--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