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: Sat, 27 Feb 2021 15:48:38 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 2021-02-25 16:16, Simon Marchi wrote:
> On 2020-12-11 12:52 p.m., Simon Marchi via Gdb wrote:
>> On 2020-12-11 12:31 p.m., Stephen Webb via Gdb wrote:
>>>> If somebody would like the support for Neutrino to stay in GDB, please
>>>   > speak up.
>>>   > If so, we will need a maintainer to step up and become responsible to
>>>   > that port.
>>> We at QNX have opened discussions internally on this. Please hold off on
>>> removal until at least the new year.
>> Ok, thanks for the heads up.  If you'd like to contribute upstream, please
>> let us know if there's anything we can do to help.
> Hi Stephen,
> Do you have any news regarding this?

We have decided to commit to integrating our fork as much as possible 
into upstream and maintaining it there.

There are a lot of steps we'll need to go through to complete this 
process, including all the legal and technical preparations. These will 
of course take time and we're going to need some guidance.

We already have pointers on BuildBot setup so we can start the ball 
rolling locally on our end. We'll start by maintaining a local patch 
queue against upstream branches and submitting them through the various 
review processes. I do not yet have a time estimate on when this will be 

Is there a link to the paperwork requirements for code submissions? The 
sooner we get the ball rolling on that the sooner we can start waiting 
for it.


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-02-27 15:48 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 [this message]
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

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