From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: RFA: Using year ranges in copyright notices...
Date: Wed, 04 Jan 2012 04:15:00 -0000 [thread overview]
Message-ID: <20120104041457.GS2730@adacore.com> (raw)
In-Reply-To: <20120103180158.GR2730@adacore.com>
[-- Attachment #1: Type: text/plain, Size: 395 bytes --]
OK, this is the latest version. I am more or less copy/pasting
the text from the maintainers' manual, so hopefully OK>
I'm about to work on updating the copyright years, so I've committed
this one. Eli, let me know if there are any additional changes you
would like me to make. I will make them within the day.
gdb/ChangeLog:
* README (Copyright and License Notices): New section.
--
Joel
[-- Attachment #2: readme.diff --]
[-- Type: text/x-diff, Size: 1627 bytes --]
commit f411a6ac0f301c50f5271aff830b84f4b70e0858
Author: Joel Brobecker <brobecker@adacore.com>
Date: Tue Jan 3 12:41:50 2012 +0400
[README] Add note about copyright and license notices
Also explain the use of year ranges in copyright notices.
gdb/ChangeLog:
* README (Copyright and License Notices): New section.
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 266f387..b68d64c 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2012-01-04 Joel Brobecker <brobecker@adacore.com>
+
+ * README (Copyright and License Notices): New section.
+
2012-01-03 Tom Tromey <tromey@redhat.com>
PR python/12533:
diff --git a/gdb/README b/gdb/README
index d79fecc..999f992 100644
--- a/gdb/README
+++ b/gdb/README
@@ -638,6 +638,26 @@ testsuite `standalone', without it being part of the GDB source tree.
See the DejaGNU documentation for further details.
+
+Copyright and License Notices
+=============================
+
+Most files maintained by the GDB Project contain a copyright notice
+as well as a license notice, usually at the start of the file.
+
+To reduce the length of copyright notices, consecutive years in the
+copyright notice can be combined into a single range. For instance,
+the following list of copyright years...
+
+ 1986, 1988, 1989, 1991-1993, 1999, 2000, 2007, 2008, 2009, 2010, 2011
+
+... is abbreviated into:
+
+ 1986, 1988-1989, 1991-1993, 1999-2000, 2007-2011
+
+Every year of each range, inclusive, is a copyrightable year that
+could be listed individually.
+
\f
(this is for editing this file with GNU emacs)
Local Variables:
next prev parent reply other threads:[~2012-01-04 4:15 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
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 [this message]
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=20120104041457.GS2730@adacore.com \
--to=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