Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Michael Elizabeth Chastain <mec@shout.net>
To: gdb-patches@sources.redhat.com, kewarken@qnx.com
Subject: Re: [patch] New testcase for PR:1291
Date: Fri, 24 Oct 2003 19:20:00 -0000	[thread overview]
Message-ID: <200310241920.h9OJKYwA024280@duracef.shout.net> (raw)

Copyright nagging: gdb1291.c needs either a copyright notice,
or an explicit notice that copyright has been abandoned and
the file is in the public domain.

(gcc has a policy that they want bug reports to include
pre-processed C source, which means all the comments were gone.
But we have no such policy.  Instead, we have a policy that all
files longer than 10 lines must have copyright notices,
including test files).

Also, Andrew says that the preferred incantation is
"this file is part of gdb", not "this file is part of the gdb
test suite".

Other than that, I don't have any stylistic complaints.
Lightly proofread.  Not tested.  Busy day for me.  :(

Michael C

Changelog:

2003-10-24  Kris Warkentin  <kewarken@qnx.com>

 * gdb.arch/gdb1291.c: New test file.
 * gdb.arch/gdb1291.exp: New test script.


             reply	other threads:[~2003-10-24 19:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-24 19:20 Michael Elizabeth Chastain [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-24 19:23 Michael Elizabeth Chastain
2003-10-27 19:01 ` Kris Warkentin
2003-10-28 16:02   ` Elena Zannoni
2003-10-28 16:46     ` Kris Warkentin
2003-10-28 16:49       ` Daniel Jacobowitz
2003-10-24 15:40 Kris Warkentin
2003-10-24 15:59 ` Daniel Jacobowitz
2003-10-24 17:46   ` Kris Warkentin
2003-10-24 17:59     ` Daniel Jacobowitz
2003-10-24 16:01 ` Elena Zannoni

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=200310241920.h9OJKYwA024280@duracef.shout.net \
    --to=mec@shout.net \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kewarken@qnx.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