public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: RFC: Add native support for Linux SH
Date: Mon, 12 Jun 2017 12:15:00 -0000	[thread overview]
Message-ID: <20170612121521.GD23760@physik.fu-berlin.de> (raw)
In-Reply-To: <CAH=s-PNYtZJ3BN8JaBu=zgc9KSUkNJo22NTb6M-j2y-DUzWjzQ@mail.gmail.com>

Hi Yao!

On Thu, Feb 16, 2017 at 09:47:51PM +0000, Yao Qi wrote:
> > Do they need to sign copyright assignments for every individual contributor
> > and every individual project?
> >
> 
> At least, you need the gdb author Yoshii-san have his copyright assignment
> for gdb.
> 
> Here are some records we have, for example,
> (...)

I finally received a reply from Takashi Yoshii. He said, his work on
gdb was made while working at Renesas Solutions Corp. and therefore
the copyright lies with them.

Unfortunately, Renesas Solutions Corp. now longer exists. The company
has been succeeded by Renesas System Design Co., Ltd.

From the Renesas website [1]:

> Regarding handling of former company name in content

> Following the reorganization of design and development departments of
> Renesas affiliates in Japan dated August 1, 2014, the device solution
> development functions of Renesas Solutions Corp. (RSO) were
> transferred to Renesas System Design Co., Ltd. (RSD) and the name of
> the company to which the departments belong was also changed from RSO
> to RSD as of August 1, 2014.
> Consequently, although the content (schematic circuit diagrams and
> bill of materials) that is provided on this page may include mention
> of the former company name, the content is still a valid Renesas
> document.

> Your understanding is most appreciated.

Do you guys have any signed statements from either of the two
companies stated above?

Yutaka Niibe is now trying to get in touch with the open-source
department of Renesas to sort the assignment out.

I have already signed the copyright assignments for my own changes on
top of Yoshii's changes.

Thanks,
Adrian

> [1] https://www.renesas.com/en-us/products/software-tools/boards-and-kits/evaluation-demo-solution-boards/r0k572690b000br.html

-- 
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
  `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  parent reply	other threads:[~2017-06-12 12:15 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 [this message]
2017-06-12 14:15         ` Yao Qi
2017-02-16 19:02   ` Mike Frysinger
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=20170612121521.GD23760@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=gdb-patches@sourceware.org \
    --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).