From: Yao Qi <qiyaoltc@gmail.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: RFC: Add native support for Linux SH
Date: Sat, 18 Feb 2017 20:07:00 -0000 [thread overview]
Message-ID: <CAH=s-PMNOQpU9TcJhKDxGND49iLhguee=oJ7wpUSMkZ3XtxLzA@mail.gmail.com> (raw)
In-Reply-To: <1faf0af5-4d7c-c769-a5e2-14b3ab25c57c@physik.fu-berlin.de>
On Sat, Feb 18, 2017 at 12:32 PM, John Paul Adrian Glaubitz
<glaubitz@physik.fu-berlin.de> wrote:
> On 02/16/2017 10:47 PM, Yao Qi wrote:
>> I'll contact to GDB FSF-appointed maintainers to see what do you
>> need.
>
> That would be very helpful. Thanks a lot!
>
We discussed it off-list, we believe that a new copyright
assignment is needed for Yoshii-san's GDB SH patch.
Yoshii-san needs one of three forms mentioned in
https://www.gnu.org/prep/maintain/html_node/Copyright-Papers.html
If Yoshii-san wants to change the code in the future, he needs
request-assign.future,
Otherwise he needs request-assign.changes or
request-disclaim.changes, depending on the size of change. We are
sure that SH native support is not a small change, but we don't know
it is a "big change" or "medium change", because the link above
doesn't give a clear definition of "big change" and "medium change".
Please ask assign@gnu.org for the advise of the which form is
appropriate in this case.
--
Yao (齐尧)
next prev parent reply other threads:[~2017-02-18 20:07 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 [this message]
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='CAH=s-PMNOQpU9TcJhKDxGND49iLhguee=oJ7wpUSMkZ3XtxLzA@mail.gmail.com' \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=glaubitz@physik.fu-berlin.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).