From: Simon Marchi <simon.marchi@polymtl.ca>
To: Stephen Webb <swebb@blackberry.com>,
"gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Proposal to Removal of QNX Neutrino support from GDB
Date: Tue, 28 Mar 2023 15:24:58 -0400 [thread overview]
Message-ID: <68acdee2-332c-1f05-699b-bba9bc9103db@polymtl.ca> (raw)
In-Reply-To: <9c2a6aa76dc942c98022e29b775cc7d8@blackberry.com>
On 8/4/21 11:14, Stephen Webb wrote:
> On 2021-08-04 10:51, Simon Marchi wrote:
>>
>>
>> On 2021-03-01 11:45 a.m., Simon Marchi via Gdb wrote:
>>>> Regarding the copyright assignment, I'd like to see what is the status
>>>> of QNX. Is there maybe an existing company-wide copyright assignment
>>>> for QNX, given the past contributions? Unfortunately, the GNU server
>>>> used to check those seems down. I'll try back later.
>>>>
>>>> If there isn't, it's possible to get an assignment for individuals, or a
>>>> company-wide one (meaning that any QNX employee can submit code to GDB).
>>>>
>>>> The typical form we point individuals to to get an assignment is this
>>>> one (also down for me at the moment):
>>>>
>>>> https://urldefense.com/v3/__https://git.savannah.gnu.org/cgit/gnulib.git/plain/doc/Copyright/request-assign.future__;!!COg3wY07Hnb7!-QdSDefYRZU83E3QoIKDECG14HQyWydyjH4yGM0yF8AikrbmXWSfBM_bHGRdXuRJ$
>>>>
>>>> But I don't know if that differs if you want to get one for someone who
>>>> will contribute on behalf of a company. The folks at assign@gnu.org
>>>> will be able to help you.
>>>>
>>>> In any case, I'd suggest sorting the copyright assignment thing as early
>>>> as possible, because that can take some time. You can still send
>>>> patches and get them reviewed while that is pending, but you won't be
>>>> able to merge the patches until that's done.
>>>
>>> I was able to take a look at the copyright assignment file. I found an
>>> entry dating from 2002-02-15 for GDB, with no name (it only mentions
>>> QNX). So it's perhaps a company-wide assignment? Hopefully that can
>>> help you find any traces of it internally. In doubt, ask
>>> assign@gnu.org, they probably have access to the detailed paperwork.
>>>
>>> Simon
>>>
>>
>> Hi Stephen
>>
>> Do you have any updates about this?
>
> I am still wrestling with internal demons on this, I apologise for the
> silence. I should have some basic binutils patches soon as a first step.
Hi Stephen,
Someone reminded me of this thread... any news on your side about
upstream contributions?
Simon
prev parent reply other threads:[~2023-03-28 19:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 14:47 Simon Marchi
2020-12-11 17:31 ` Stephen Webb
2020-12-11 17:52 ` Simon Marchi
2021-02-25 21:16 ` Simon Marchi
2021-02-27 15:48 ` Stephen Webb
2021-02-28 15:28 ` Simon Marchi
2021-03-01 16:45 ` Simon Marchi
2021-08-04 14:51 ` Simon Marchi
2021-08-04 15:14 ` Stephen Webb
2021-08-04 17:21 ` Simon Marchi
2021-08-04 19:47 ` Luis Machado
2022-04-05 14:30 ` Simon Marchi
2023-03-28 19:24 ` Simon Marchi [this message]
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=68acdee2-332c-1f05-699b-bba9bc9103db@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb@sourceware.org \
--cc=swebb@blackberry.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).