public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: Re: RFC: one more question about year ranges in copyright notices...
Date: Fri, 27 Jan 2012 09:23:00 -0000	[thread overview]
Message-ID: <20120127054738.GA28443@adacore.com> (raw)
In-Reply-To: <20120106062310.GH2730@adacore.com>

Hello again,

> Thanks a lot to all of you who answered. Very helpful. As usual
> when it comes to legal matters, I did not have a clear understanding
> of the all the ramifications. I have therefore sent the question
> to the FSF copyright clerk email address.
> 
> One small clarification: The proposed change will simply shrink
> the copyright years into a single range, but it will not change
> the initial year recorded in each file. If that initial year is
> mistaken (in either direction), fixing that would need to be done
> on an individual basis after review.

I just got an answer from the FSF (case [gnu.org #719834]), and
it is fine to shrink the copyright year list into a single range,
even if there are "holes" in the original year list.

I will put this on my list of things to do sometime next month
(which ironically is in a few days - where does time go?).

-- 
Joel

      reply	other threads:[~2012-01-27  5:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-04  9:47 Joel Brobecker
2012-01-04 16:10 ` Tom Tromey
2012-01-04 16:19 ` Stan Shebs
2012-01-04 16:43   ` Tom Tromey
2012-01-04 16:55   ` Pedro Alves
2012-01-04 17:17     ` Joseph S. Myers
2012-01-04 17:38       ` Alfred M. Szmidt
2012-01-04 17:28   ` Alfred M. Szmidt
2012-01-06  6:23 ` Joel Brobecker
2012-01-27  9:23   ` Joel Brobecker [this message]

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=20120127054738.GA28443@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).