From: Michael Matz <matz@suse.de>
To: Tom de Vries <tdevries@suse.de>
Cc: Jakub Jelinek <jakub@redhat.com>, dwz@sourceware.org
Subject: Re: [PATCH] Add do-release.sh
Date: Tue, 01 Jan 2019 00:00:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1908011519270.25869@wotan.suse.de> (raw)
In-Reply-To: <e8623c38-c281-8839-02bc-7cf74ec4edb0@suse.de>
Hi,
On Thu, 1 Aug 2019, Tom de Vries wrote:
> > One thing that might be worth doing is bump copyright years on files you've
> > modified, I know dwz.c has been using mostly Red Hat copyright, if you want
> > to use say FSF copyright, can you change that 2003 in there to 2003, 2019?
> > Or do you want to use SUSE copyright instead?
>
> It seems I have to use the SUSE copyright.
Maybe background on this:
The FSF generally accepts copyright assignment only for FSF-copyrighted
GNU software (http://www.gnu.org/philosophy/categories.html#GNUsoftware,
and the following paragraph), and dwz is no GNU software
(https://directory.fsf.org/wiki/GNU), even if it uses the GPL.
So, technically, because of the impossible assignment, the copyright
remains with whomever wrote the code initially. If dwz were
FSF-copyrighted software we would have preferred the FSF attribution in
this case.
(Of course, in the end, this is all fairly minor ;-) )
Ciao,
Michael.
next prev parent reply other threads:[~2019-08-01 15:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-01 0:00 Tom de Vries
2019-01-01 0:00 ` Jakub Jelinek
2019-01-01 0:00 ` Tom de Vries
2019-01-01 0:00 ` [committed] Update --version copyright message Tom de Vries
2019-01-01 0:00 ` Branch creation: dwz-0.13-branch Tom de Vries
2019-01-01 0:00 ` [PATCH] Add do-release.sh Tom de Vries
2019-01-01 0:00 ` Jakub Jelinek
2019-01-01 0:00 ` Tom de Vries
2019-01-01 0:00 ` Michael Matz [this message]
2019-01-01 0:00 ` [committed] Copy dwarf2.def, dwarf2.h and dwarfnames.c from gcc Tom de Vries
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=alpine.LSU.2.21.1908011519270.25869@wotan.suse.de \
--to=matz@suse.de \
--cc=dwz@sourceware.org \
--cc=jakub@redhat.com \
--cc=tdevries@suse.de \
/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).