From: ams@gnu.org (Alfred M. Szmidt)
To: Eli Zaretskii <eliz@gnu.org>
Cc: brobecker@adacore.com, gdb-patches@sourceware.org
Subject: Re: RFA: Using year ranges in copyright notices...
Date: Tue, 03 Jan 2012 06:58:00 -0000 [thread overview]
Message-ID: <E1RhyJs-0004Cy-B8@fencepost.gnu.org> (raw)
In-Reply-To: <E1Rhxs0-00008Y-05@fencepost.gnu.org> (message from Eli Zaretskii on Tue, 03 Jan 2012 01:29:12 -0500)
> A bit of a trivial question, but I wanted to be sure it's OK to do so.
> I would like us to use address ranges in our copyright headers, instead
> of explicitly listing each and every year.
This needs to be cleared with lawyers @gnu.org. At least at some
point, Richard explicitly asked _not_ to use ranges, due to some
legal issues, and I don't think I saw that restriction lifted since
then.
At the very least, we should ask Richard about that.
It is documented in (maintain) Copyright Notices:
| You can use a range (`2008-2010') instead of listing individual
| years (`2008, 2009, 2010') if and only if: 1) every year in the range,
| inclusive, really is a "copyrightable" year that would be listed
| individually; _and_ 2) you make an explicit statement in a `README'
| file about this usage.
next prev parent reply other threads:[~2012-01-03 6:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 4:24 Joel Brobecker
2012-01-03 6:29 ` Eli Zaretskii
2012-01-03 6:58 ` Alfred M. Szmidt [this message]
2012-01-03 7:16 ` Joel Brobecker
2012-01-03 8:53 ` Joel Brobecker
2012-01-03 9:48 ` Yao Qi
2012-01-03 10:15 ` Joel Brobecker
2012-01-03 15:47 ` Joseph S. Myers
2012-01-03 16:02 ` Joel Brobecker
2012-01-03 17:53 ` Jan Kratochvil
2012-01-03 18:02 ` Joel Brobecker
2012-01-04 4:15 ` Joel Brobecker
2012-01-04 5:22 ` Eli Zaretskii
2012-01-03 10:59 ` Eli Zaretskii
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=E1RhyJs-0004Cy-B8@fencepost.gnu.org \
--to=ams@gnu.org \
--cc=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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