From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: gdb-patches@sources.redhat.com
Subject: [rfa/testsuite/copyright] callfuncs.c: add copyright notice
Date: Wed, 14 Jan 2004 06:05:00 -0000 [thread overview]
Message-ID: <20040114060551.E42F64B104@berman.michael-chastain.com> (raw)
This patch adds a copyright notice to gdb.base/callfuncs.c.
I sent a message to gdb@ on 2004-01-06 asking for copyright years on
callfuncs.c. I got one message back from Jim Blandy, who said that the
file was created in 1993. This matches the information that I found.
I obtained the list of years from two sources: testsuite/ChangeLog,
which goes back to its creation in 1993, and the modification times on
callfuncs.c in gdb releases going back to gdb 4.13 in 1994.
Testing: tested on native i686-pc-linux-gnu, gcc 2.95.3 3.3.2 HEAD,
dwarf-2 and stabs+ (to make sure that there are no line number
dependencies in callfuncs.exp).
I need to fix callfuncs.c so that it works on hp-ux, and adding a
copyright notice is the first step.
Okay to commit?
Michael C
2004-01-08 Michael Chastain <mec.gnu@mindspring.com>
* gdb.base/callfuncs.c: Add copyright notice.
Index: callfuncs.c
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/callfuncs.c,v
retrieving revision 1.4
diff -c -3 -p -r1.4 callfuncs.c
*** callfuncs.c 26 Nov 2001 21:29:31 -0000 1.4
--- callfuncs.c 8 Jan 2004 20:09:11 -0000
***************
*** 1,3 ****
--- 1,25 ----
+ /* This testcase is part of GDB, the GNU debugger.
+
+ Copyright 1993, 1994, 1995, 1998, 1999, 2000, 2001
+ Free Software Foundation, Inc.
+
+ This program is free software; you can redistribute it and/or modify
+ it under the terms of the GNU General Public License as published by
+ the Free Software Foundation; either version 2 of the License, or
+ (at your option) any later version.
+
+ This program is distributed in the hope that it will be useful,
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
+ GNU General Public License for more details.
+
+ You should have received a copy of the GNU General Public License
+ along with this program; if not, write to the Free Software
+ Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA.
+
+ Please email any bugs, comments, and/or additions to this file to:
+ bug-gdb@prep.ai.mit.edu */
+
/* Support program for testing gdb's ability to call functions
in the inferior, pass appropriate arguments to those functions,
and get the returned result. */
next reply other threads:[~2004-01-14 6:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-14 6:05 Michael Elizabeth Chastain [this message]
2004-01-14 13:55 ` Daniel Jacobowitz
2004-01-14 14:13 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=20040114060551.E42F64B104@berman.michael-chastain.com \
--to=mec.gnu@mindspring.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