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: Fri, 28 Feb 2014 18:22:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1402281818151.14521@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20140228130844.GA4893@adacore.com>
On Fri, 28 Feb 2014, Joel Brobecker wrote:
> > Joseph, do you know why implicitly adding years to the claimed
> > copyright years is a problem? I'm guessing the file needs to be
> > published somewhere for each year claimed.
>
> IANAL, but from 2 discussions with copyright-clerk:
>
> 1. We start claiming copyright the year the file as committed
> to a medium (hard drive), not the year it was published.
I don't think it counts unless the version in question got published at
some point. The question is about versions that weren't published at the
time, but were published later when the version control history was
released.
There was a discussion on bug-standards starting Jan 2012. Karl's revised
wording from 11 May 2012 seems to indicate that if a version was committed
to a version control history that was later released, the dates from that
history count as copyrightable years (so reducing the number of cases
where it may not be possible to fill in gaps) - but that revised wording
doesn't seem to have been committed.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2014-02-28 18:22 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
2014-02-28 8:57 ` Alan Modra
2014-02-28 13:08 ` Joel Brobecker
2014-02-28 18:22 ` Joseph S. Myers [this message]
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.1402281818151.14521@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