From: Jim Blandy <jimb@redhat.com>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: cagney@redhat.com, gdb@sources.redhat.com
Subject: Re: copyright years for callfuncs.c ?
Date: Fri, 09 Jan 2004 00:01:00 -0000 [thread overview]
Message-ID: <vt265fmgfmi.fsf@zenia.home> (raw)
In-Reply-To: <20040107014403.EAF594B35A@berman.michael-chastain.com>
mec.gnu@mindspring.com (Michael Elizabeth Chastain) writes:
> I'm fixing to fix testsuite/gdb.base/callfuncs.c for hp-ux
> (it's trivial, it has its own bogus declaration of malloc
> instead of #include <stdlib.h> like 22 other files already do).
>
> callfuncs.c needs a copyright header. Andrew C, or somebody,
> can you look in the old Cygnus repository and give me a list of years?
The oldest revision I can find is this:
revision 1.1
date: 1993/03/17 19:33:38; author: fnf; state: Exp;
* gdb.t17/{Makefile.in, callfuncs.exp, gdbme.c}: New test
files to test gdb's calling of functions in the inferior with
the correct arguments and gdb's ability to retrieve any
result returned.
GDB 4.9 was released sometime in 1993, so 1993 belongs in the list of
years, but nothing older.
prev parent reply other threads:[~2004-01-09 0:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 1:43 Michael Elizabeth Chastain
2004-01-09 0:01 ` Jim Blandy [this message]
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=vt265fmgfmi.fsf@zenia.home \
--to=jimb@redhat.com \
--cc=cagney@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.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