From: Andrew Cagney <cagney@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: cagney@redhat.com, ezannoni@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [rfa/testsuite/mi/copyright] basics.c, var-cmd.c: add copyright notice
Date: Tue, 24 Aug 2004 22:54:00 -0000 [thread overview]
Message-ID: <412BC6C1.1080104@gnu.org> (raw)
In-Reply-To: <4121EDC0.nail9EU1ZPKM2@mindspring.com>
> Ha. It turns out that all of the files which use pthreads.c are already
> line-number-independent. So I'm finished adding gdb_get_line_number.
>
> Here is the next phase for making gdb.mi work with gcc HEAD:
> adding copyright notices to several files.
>
> Fernando Nasser created basics.c in 1999.
> It was last edited in 2000.
>
> Elena Zannoni created var-cmd.c in 1999.
> Andrew Cagney committed it to CVS in 2000.
> It hasn't been edited since then.
> I assume that the file wasn't edited in 2000, either.
>
> Data sources: cvs log, testsuite/gdb.mi/ChangeLog-1999-2003,
> testsuite/ChangeLog, historical gdb releases, and the
> gdb-patches mailing list for 1999q4 and 2000q1.
>
> Tested on native i686-pc-linux-gnu with gcc 2.95.3, gcc 3.3.4,
> and gcc 3.4.1, with dwarf-2 and stabs+.
>
> After this, the next phase will be the addition of several
> "#include" lines to several *.c files so that they compile
> with gcc HEAD with no warnings.
Both ok. I think we can largly view this stuff as mindless (no offence
:-) mechanical, and effectively obviousish.
Andrew
> 2004-08-17 Michael Chastain <mec.gnu@mindspring.com>
>
> * gdb.mi/basics.c: Add copyright notice.
> * gdb.mi/var-cmd.c: Add copyright notice.
>
next prev parent reply other threads:[~2004-08-24 22:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-17 11:36 Michael Chastain
2004-08-24 22:54 ` Andrew Cagney [this message]
2004-08-25 1:06 ` Michael 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=412BC6C1.1080104@gnu.org \
--to=cagney@gnu.org \
--cc=cagney@redhat.com \
--cc=ezannoni@redhat.com \
--cc=gdb-patches@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