From: Daniel Black <daniel@mariadb.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 3/6] Manual copyright year update of various GDB files
Date: Mon, 10 Jan 2022 17:47:49 +1100 [thread overview]
Message-ID: <CABVffEPPvva8+cBVYKDo4tU-WQRg50zvDgne74ekfgbk9fLkiw@mail.gmail.com> (raw)
In-Reply-To: <YdvGLwkjosRa4p8i@adacore.com>
On Mon, Jan 10, 2022 at 4:37 PM Joel Brobecker <brobecker@adacore.com> wrote:
>
> > On Sun, Jan 2, 2022 at 2:14 AM Joel Brobecker via Gdb-patches
> > <gdb-patches@sourceware.org> wrote:
> >
> > > gdb/doc/refcard.tex | 4 ++--
> >
> > How do you claim new copyright in this file when the last
> > (non-copyright notice) change was in 2012 (168997566e2a)?
> >
> > The other files seem reasonable based on the frequency of changes.
>
> Unfortunately, I am not a lawyer and cannot answer your question.
> We are applying here our understanding here of what we were told
> by the FSF we could do.
It doesn't seem right (ref: "The copyright notice"
http://www.gnu.org/licenses/gpl-howto.html).
Replacing "release" for "file" as equivalent copyrightable object
would be when the last change ("creative work") was written
to the file as the minimum criteria.
"For software with several releases .. use a range (“2008-2010”) ...
if and only if every year in the range, inclusive, really is a
“copyrightable” year that would be listed individually; and ...
The non-legal, but endorsed, and not (publicly/locally) contended
verbose description:
https://softwareengineering.stackexchange.com/questions/210472/is-renewal-of-mit-license-needed-on-github-at-the-beginning-of-each-year
A pre-release/end of year process that accounts for changes would seem
more respectful of what copyright is, in my not-a-lawyer opinion
anyway.
next prev parent reply other threads:[~2022-01-10 6:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-01 15:12 [FYI] GDB Start of New Year Procedure Joel Brobecker
2022-01-01 15:12 ` [PATCH 1/6] Update Copyright Year in gdb, gdbserver and gdbreplay version output Joel Brobecker
2022-01-01 15:12 ` [PATCH 3/6] Manual copyright year update of various GDB files Joel Brobecker
2022-01-10 5:10 ` Daniel Black
2022-01-10 5:37 ` Joel Brobecker
2022-01-10 6:47 ` Daniel Black [this message]
2022-01-10 17:29 ` Eli Zaretskii
2022-01-01 15:12 ` [PATCH 4/6] gdb/copyright.py: Add update-netbsd.sh to MULTIPLE_COPYRIGHT_HEADERS Joel Brobecker
2022-01-01 15:12 ` [PATCH 5/6] Fix copyright header in gdb/testsuite/gdb.arch/powerpc-power10.exp Joel Brobecker
2022-01-01 15:12 ` [PATCH 6/6] Update Copyright year " Joel Brobecker
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=CABVffEPPvva8+cBVYKDo4tU-WQRg50zvDgne74ekfgbk9fLkiw@mail.gmail.com \
--to=daniel@mariadb.org \
--cc=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).