Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: <binutils@sourceware.org>, <gdb-patches@sourceware.org>,
	<gcc-patches@gcc.gnu.org>
Subject: Re: copyright dates in binutils (and includes/)
Date: Thu, 27 Feb 2014 18:47:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1402271845060.27019@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20140227132551.GO4348@adacore.com>

On Thu, 27 Feb 2014, Joel Brobecker wrote:

> I should mention, however, that for us to use ranges like this,
> the FSF asked us to add a note explaining that the copyright years
> could be abbreviated into a range. See gdb/README (at the end).
> I suspect that you'll need the same note for binutils.

And, where a gap in the years is being implicitly filled in by conversion 
to a range, make sure that either (a) there was a public version control 
repository for binutils during that year, or (b) there was a release 
(including beta releases, Cygnus releases etc., not just official 
releases) during that year.

-- 
Joseph S. Myers
joseph@codesourcery.com


  reply	other threads:[~2014-02-27 18:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-27  4:50 Alan Modra
2014-02-27 13:25 ` Joel Brobecker
2014-02-27 18:47   ` Joseph S. Myers [this message]
2014-02-28  8:57     ` Alan Modra
2014-02-28 13:08       ` Joel Brobecker
2014-02-28 18:22         ` Joseph S. Myers
2014-03-03  3:45           ` Alan Modra
2014-03-03  4:16             ` Alan Modra
2014-03-03 13:33               ` Richard Sandiford
2014-03-05 12:34                 ` Alan Modra

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=Pine.LNX.4.64.1402271845060.27019@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=binutils@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=gcc-patches@gcc.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