From: Robert Dewar <dewar@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sources.redhat.com
Subject: Re: Copyright notices
Date: Sun, 12 Feb 2006 03:15:00 -0000 [thread overview]
Message-ID: <43EEA845.2060202@adacore.com> (raw)
In-Reply-To: <u8xshyhxf.fsf@gnu.org>
Eli Zaretskii wrote:
> IANAL, but I'm guessing that erring on the other side, i.e. forgetting
> to add a year when changes _were_ made, is being considered a greater
> evil.
Probably so, although since copyright notices since 1986 have
no real legal significance there is no danger of evil whatever
is done.
next prev parent reply other threads:[~2006-02-12 3:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 11:08 Eli Zaretskii
2006-02-11 11:13 ` Robert Dewar
2006-02-11 16:33 ` Eli Zaretskii
2006-02-12 3:15 ` Robert Dewar [this message]
2006-02-11 14:36 ` Daniel Jacobowitz
2006-02-11 16:30 ` Eli Zaretskii
2006-02-11 18:27 ` Daniel Jacobowitz
2006-02-11 19:05 ` Eli Zaretskii
2006-02-11 19:07 ` Daniel Jacobowitz
2006-02-11 19:18 ` Eli Zaretskii
2006-02-11 20:31 ` Daniel Jacobowitz
2006-02-11 19:19 ` Bob Rossi
2006-02-11 21:55 ` Eli Zaretskii
2006-02-12 6:09 ` Jim Blandy
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=43EEA845.2060202@adacore.com \
--to=dewar@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb@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