Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: RFA: Using year ranges in copyright notices...
Date: Tue, 03 Jan 2012 04:24:00 -0000	[thread overview]
Message-ID: <20120103042431.GI2730@adacore.com> (raw)

Hello,

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.  One striking example would
be valprint.c:

-   Copyright (C) 1986, 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996,
-   1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008,
-   2009, 2010, 2011 Free Software Foundation, Inc.
+   Copyright (C) 1986, 1988-2012 Free Software Foundation, Inc.

Here is how it would look like for typeprint.h, for instance:

-   Copyright (C) 1986, 1988, 1989, 1991-1993, 1999, 2000, 2007, 2008, 2009,
-   2010, 2011 Free Software Foundation, Inc.
+   Copyright (C) 1986, 1988-1989, 1991-1993, 1999-2000, 2007-2012 Free
+   Software Foundation, Inc.

Any objection? A quick answer would be appreciated, as I am planning
on folding this change with the copyright year update commit.
Committing this massive change takes a lot of time, so I'd rather
only have to do one of them.

Thanks,
-- 
Joel


             reply	other threads:[~2012-01-03  4:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-03  4:24 Joel Brobecker [this message]
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
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=20120103042431.GI2730@adacore.com \
    --to=brobecker@adacore.com \
    --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