public inbox for
 help / color / mirror / Atom feed
From: Stephen Webb <>
To: Simon Marchi <>,
	"" <>
Subject: Re: Proposal to Removal of QNX Neutrino support from GDB
Date: Wed, 4 Aug 2021 15:14:13 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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):
>>> 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
>>> 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
>>, 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.

On that topic, are binutils changes handled the same as gdb changes or 
are they a separate process? The history is very confusing.


This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.

  reply	other threads:[~2021-08-04 15:14 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 [this message]
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

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).