From: Andrew Cagney <cagney@gnu.org>
To: Michael Elizabeth Chastain <mec.gnu@mindspring.com>
Cc: gdb-patches@sources.redhat.com, hunt@redhat.com
Subject: Re: [commit/6.2] Fix lib (C)s; Was: src/gdb/testsuite ChangeLog lib/insight-suppor ...
Date: Mon, 19 Jul 2004 21:58:00 -0000 [thread overview]
Message-ID: <40FC4409.70809@gnu.org> (raw)
In-Reply-To: <20040719213147.AEC014B104@berman.michael-chastain.com>
> ac> As with a book, this file contains two things: the "work" (i.e., the tcl
> ac> code) and the (C) notice. Changes to the (C) notice / terms do not
> ac> create a new "work", only modifications to the "work" do..
>
> I think the boilerplate text also constitutes part of the work.
>
> I see your position, but I don't agree. I'm going to add a "2004"
> to this file.
Given that the boilerplate "work" is stolen from COPYING and that has a
(C) of 1989,1991 why should you not instead be adding those dates (and
have those dates through out all of GDB's files)?
Andrew
next prev parent reply other threads:[~2004-07-19 21:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-19 21:31 Michael Elizabeth Chastain
2004-07-19 21:58 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-20 20:50 Michael Elizabeth Chastain
2004-07-20 5:18 Michael Elizabeth Chastain
2004-07-20 17:34 ` Daniel Berlin
2004-07-19 22:33 Michael Elizabeth Chastain
2004-07-20 1:07 ` Andrew Cagney
2004-07-20 1:41 ` Daniel Berlin
2004-07-17 20:36 Michael Elizabeth Chastain
2004-07-19 14:25 ` Andrew Cagney
2004-07-17 2:40 Michael Elizabeth Chastain
2004-07-17 2:56 ` Andrew Cagney
2004-07-14 20:46 Michael Elizabeth Chastain
2004-07-14 21:59 ` Martin M. Hunt
2004-07-17 2:09 ` [commit/6.2] Fix lib (C)s; Was: " Andrew Cagney
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=40FC4409.70809@gnu.org \
--to=cagney@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=hunt@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