Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Carlton <carlton@math.stanford.edu>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Cc: carlton@math.stanford.edu
Subject: Re: [rfa/testsuite] more tests in gdb.c++/m-static
Date: Fri, 16 Aug 2002 14:37:00 -0000	[thread overview]
Message-ID: <ro1bs82wkn1.fsf@jackfruit.Stanford.EDU> (raw)
In-Reply-To: <20020816213122.GA12044@nevyn.them.org>

In article <20020816213122.GA12044@nevyn.them.org>, Daniel Jacobowitz <drow@mvista.com> writes:
> On Fri, Aug 16, 2002 at 02:19:35PM -0700, David Carlton wrote:

>> * 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.

Makes sense.

> 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.)

Thanks for the tip.  I inherited that from the pre-existing
m-static.cc file; to be honest, I have no idea why that file uses
namespaces at all, let alone namespaces beginning with two
underscores.  But if I add more tests myself, I'll make sure to avoid
such underscores.

David Carlton
carlton@math.stanford.edu


  reply	other threads:[~2002-08-16 21:37 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
2002-08-16 14:37   ` David Carlton [this message]
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=ro1bs82wkn1.fsf@jackfruit.Stanford.EDU \
    --to=carlton@math.stanford.edu \
    --cc=drow@mvista.com \
    --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