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, 13 Feb 2017 22:31:00 -0000 [thread overview]
Message-ID: <b1b236e0-fba2-80d5-21c2-177e6fc615e5@physik.fu-berlin.de> (raw)
In-Reply-To: <CAH=s-PNzmpG0h2jabC+4+Q=9=xkEJN+1z9R7U1bTb4BnKeDyNg@mail.gmail.com>
On 02/13/2017 11:27 PM, Yao Qi wrote:
> 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.
Do they need to sign copyright assignments for every individual contributor
and every individual project?
In any case, I am working to get in touch with the right people at Renesas
to get this resolved. But I need to know what exactly I need.
Thanks,
Adrian
--
.''`. 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
next prev parent reply other threads:[~2017-02-13 22:31 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 [this message]
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
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=b1b236e0-fba2-80d5-21c2-177e6fc615e5@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).