From patchwork Sat Jun 30 14:58:23 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Joseph Myers X-Patchwork-Id: 168299 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from sourceware.org (server1.sourceware.org [209.132.180.131]) by ozlabs.org (Postfix) with SMTP id E96A52C007B for ; Sun, 1 Jul 2012 00:59:01 +1000 (EST) Comment: DKIM? See http://www.dkim.org DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=gcc.gnu.org; s=default; x=1341673143; h=Comment: DomainKey-Signature:Received:Received:Received:Received:Received: Received:Received:Date:From:To:Subject:Message-ID:MIME-Version: Content-Type:Mailing-List:Precedence:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:Sender:Delivered-To; bh=NRRVdr7 JaJXG2kscDUox1mrQdVM=; b=aF/5M67KM8rF0j2Jm4XtEldPgIzZLEvmHAEoTgu vBR3ayyl+FDRtl/0T0M3gTgesIRnfpouLyv0+UPSTsNEiAjETD+MPljiahcIGMwQ yfSEmDwbjFaKxV/+QExJQ1iNeahgWG/be57v90kyetI9iQkK+XjNIYNJE1vQuPSI YchU= Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=gcc.gnu.org; h=Received:Received:X-SWARE-Spam-Status:X-Spam-Check-By:Received:Received:Received:Received:Received:Date:From:To:Subject:Message-ID:MIME-Version:Content-Type:Mailing-List:Precedence:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help:Sender:Delivered-To; b=qgNOgdlLxeMqD4Ta+0K2EVeOwVelHyrnOCQaTHnqsGr3WTwi2BY8w7GpSaxpzG KBe97mshz+G1O4S13J+6IcmWeEpxg1uSpbCO0UEs40aMsOsAyh7njz6WoWC6aU7t OzztzBldKvF24RLpwKimJIeREVC7LgcpPvdElnnoLpHNc=; Received: (qmail 18807 invoked by alias); 30 Jun 2012 14:58:54 -0000 Received: (qmail 18789 invoked by uid 22791); 30 Jun 2012 14:58:51 -0000 X-SWARE-Spam-Status: No, hits=-4.2 required=5.0 tests=AWL, BAYES_00, KHOP_RCVD_UNTRUST, RCVD_IN_HOSTKARMA_W, RCVD_IN_HOSTKARMA_WL X-Spam-Check-By: sourceware.org Received: from relay1.mentorg.com (HELO relay1.mentorg.com) (192.94.38.131) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 30 Jun 2012 14:58:28 +0000 Received: from svr-orw-fem-01.mgc.mentorg.com ([147.34.98.93]) by relay1.mentorg.com with esmtp id 1Skz7z-0004l6-6i from joseph_myers@mentor.com ; Sat, 30 Jun 2012 07:58:27 -0700 Received: from SVR-IES-FEM-01.mgc.mentorg.com ([137.202.0.104]) by svr-orw-fem-01.mgc.mentorg.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Sat, 30 Jun 2012 07:58:26 -0700 Received: from digraph.polyomino.org.uk (137.202.0.76) by SVR-IES-FEM-01.mgc.mentorg.com (137.202.0.104) with Microsoft SMTP Server id 14.1.289.1; Sat, 30 Jun 2012 15:58:24 +0100 Received: from jsm28 (helo=localhost) by digraph.polyomino.org.uk with local-esmtp (Exim 4.76) (envelope-from ) id 1Skz7v-0007W6-La; Sat, 30 Jun 2012 14:58:23 +0000 Date: Sat, 30 Jun 2012 14:58:23 +0000 From: "Joseph S. Myers" To: , Subject: Allow use of ranges in copyright notices Message-ID: MIME-Version: 1.0 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Delivered-To: mailing list gcc-patches@gcc.gnu.org I propose that GCC should allow the use of ranges of years (e.g. 1987-2012) in copyright notices on source files. As described at : * This requires a notice in README about the use of range notation; I propose such a notice below. * It is not necessary to track the modification dates of individual files, only the package as a whole; as there have been public GCC releases or public version control in each year from 1987 onwards, the form -2012 is OK for all GCC source files (whose source is in GCC rather than being copied from another package) as long as is 1987 or later. Comments? GDB and glibc already make active use of ranges (as does the Ada front end in GCC). I think it's a useful cleanup to convert source files to the -2012 form, and to set up automatic updates of all files at the start of the year so people don't need to care about copyright notice updates for the rest of the year, but don't plan to work on these things myself. (gnulib has a script that can help with both of those things. glibc has been converting individual files to the single range form whenever the dates needed updating to include 2012, but may do a general bulk conversion later.) 2012-06-30 Joseph Myers * README: Document use of ranges of years in copyright notices. Index: README =================================================================== --- README (revision 189094) +++ README (working copy) @@ -15,3 +15,8 @@ version of the manual is in the files gcc/doc/gcc.info*. See http://gcc.gnu.org/bugs/ for how to report bugs usefully. + +Copyright years on GCC source files may be listed using range +notation, e.g., 1987-2012, indicating that every year in the range, +inclusive, is a copyrightable year that could otherwise be listed +individually.