public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Subject: Re: RFA: Using year ranges in copyright notices...
Date: Tue, 03 Jan 2012 16:02:00 -0000	[thread overview]
Message-ID: <20120103160222.GN2730@adacore.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1201031540260.14666@digraph.polyomino.org.uk>

[-- Attachment #1: Type: text/plain, Size: 701 bytes --]

> > +Such ranges are used when nontrivial changes were made to that file
> > +each and every year in the range (inclusive).
> 
> The FSF rule for listing a year is "nontrivial changes to the package" 
> rather than "to that file" (this is the basis on which it's OK to update 
> the year in all files at the start of the year).  As I understand it, this 
> combines with the rule about ranges to allow "<first-year>-2012" for every 
> file (at least, if there is some version in version control from each year 
> in the range).

That's a good point, thank you.

I propose we simply remove that sentence, then. It's not really
all that necessary, after all. Here is a new revision.

Thoughts?
-- 
Joel

[-- Attachment #2: readme.diff --]
[-- Type: text/x-diff, Size: 1335 bytes --]

commit 04d2588d202f0bc2f49e68aff22c152ec8cd277a
Author: Joel Brobecker <brobecker@adacore.com>
Date:   Tue Jan 3 12:41:50 2012 +0400

    [README] Add not 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/README b/gdb/README
index d79fecc..7ffe90a 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
+
+Such ranges are used when nontrivial changes were made to that file
+each and every year in the range (inclusive).
+
 \f
 (this is for editing this file with GNU emacs)
 Local Variables:

  reply	other threads:[~2012-01-03 16:02 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 [this message]
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=20120103160222.GN2730@adacore.com \
    --to=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=joseph@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).