From: Mike Frysinger <vapier@gentoo.org>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: RFC: Add native support for Linux SH
Date: Thu, 16 Feb 2017 19:02:00 -0000 [thread overview]
Message-ID: <20170216190251.GQ28432@vapier> (raw)
In-Reply-To: <CAH=s-PNzmpG0h2jabC+4+Q=9=xkEJN+1z9R7U1bTb4BnKeDyNg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]
On 13 Feb 2017 22:27, Yao Qi wrote:
> On Fri, Feb 10, 2017 at 8:55 PM, John Paul Adrian Glaubitz wrote:
> > With this post, I would like to ask for some feedback on how to
> > proceed with this patch. The original author of the patch is
> > Takashi Yoshii who wrote it while working at Renesas Electronics
> > in Japan.
> >
> > Back in 2011, one of the major show-stoppers why the patch was
> > not merged was apparently the missing FSF copyright assignment
> > by the author [2]. However, since Yoshii-san was working for
> > Renesas back then, I think the copyright assignment would have
> > to be signed by them and not him personally. And since Renesas
> > has already contributed various SuperH code to various FSF
> > projects like gcc and binutils, I'd assume that the necessary
> > FSF copyright assignment has already been signed.
>
> As far as I can see, the missing copyright assignment is still an issue.
> Renesas does contribute to various FSF projects, and they do have
> copy right assignments for these projects, like gcc, binutils and glibc.
> However, they don't have a copy right assignment for gdb for the author
> Yoshii-san.
if the work is done for a company, and that company has assignment
in place, the individual authors don't need papers.
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-02-16 19:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 21:03 John Paul Adrian Glaubitz
2017-02-10 21:03 ` [PATCH] gdb: " John Paul Adrian Glaubitz
2017-02-13 18:57 ` Luis Machado
2017-02-13 18:59 ` John Paul Adrian Glaubitz
2017-02-10 21:06 ` RFC: " John Paul Adrian Glaubitz
2017-02-13 22:27 ` Yao Qi
2017-02-13 22:31 ` John Paul Adrian Glaubitz
2017-02-16 21:48 ` Yao Qi
2017-02-18 12:32 ` John Paul Adrian Glaubitz
2017-02-18 20:07 ` Yao Qi
2017-03-10 10:50 ` Yao Qi
2017-03-10 10:53 ` John Paul Adrian Glaubitz
2017-06-12 12:15 ` John Paul Adrian Glaubitz
2017-06-12 14:15 ` Yao Qi
2017-02-16 19:02 ` Mike Frysinger [this message]
2018-06-21 9:49 ` John Paul Adrian Glaubitz
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=20170216190251.GQ28432@vapier \
--to=vapier@gentoo.org \
--cc=gdb-patches@sourceware.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=qiyaoltc@gmail.com \
/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).