From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-pc11.blackberry.com (smtp-pc11.blackberry.com [74.82.81.43]) by sourceware.org (Postfix) with ESMTPS id 085113887031 for ; Sat, 27 Feb 2021 15:48:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 085113887031 Received: from pps.filterd (mhs401cnc.rim.net [127.0.0.1]) by mhs401cnc.rim.net (8.16.0.43/8.16.0.43) with SMTP id 11RFjJLb174861; Sat, 27 Feb 2021 10:48:39 -0500 Received: from xch214ykf.rim.net (xch214ykf.rim.net [10.2.27.114]) by mhs401cnc.rim.net with ESMTP id 36yju1gga7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Sat, 27 Feb 2021 10:48:39 -0500 Received: from XCH214CNC.rim.net (10.3.27.119) by XCH214YKF.rim.net (10.2.27.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2044.4; Sat, 27 Feb 2021 10:48:38 -0500 Received: from XCH214CNC.rim.net ([fe80::e9f6:b8c4:f709:19e5]) by XCH214CNC.rim.net ([fe80::e9f6:b8c4:f709:19e5%4]) with mapi id 15.01.2044.012; Sat, 27 Feb 2021 10:48:38 -0500 From: Stephen Webb To: Simon Marchi , "gdb@sourceware.org" Subject: Re: Proposal to Removal of QNX Neutrino support from GDB Thread-Topic: Proposal to Removal of QNX Neutrino support from GDB Thread-Index: AQHWz+Zko67Ewa6B30mQm1hRWSaapQ== Date: Sat, 27 Feb 2021 15:48:38 +0000 Message-ID: <9d57a0ab883243e98ae1e357200e34c6@blackberry.com> References: <4205d383-e98e-f591-9031-f48925634c65@polymtl.ca> <44ea4b55-6ba2-77b2-adf4-12faa2fcad9d@polymtl.ca> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [100.64.197.236] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.369, 18.0.761 definitions=2021-02-27_10:2021-02-26, 2021-02-27 signatures=0 X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_PASS autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 27 Feb 2021 15:48:54 -0000 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, plea= se >> let us know if there's anything we can do to help. >=20 > Hi Stephen, >=20 > Do you have any news regarding this? We have decided to commit to integrating our fork as much as possible=20 into upstream and maintaining it there. There are a lot of steps we'll need to go through to complete this=20 process, including all the legal and technical preparations. These will=20 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=20 rolling locally on our end. We'll start by maintaining a local patch=20 queue against upstream branches and submitting them through the various=20 review processes. I do not yet have a time estimate on when this will be=20 ready. Is there a link to the paperwork requirements for code submissions? The=20 sooner we get the ball rolling on that the sooner we can start waiting=20 for it. -- smw ---------------------------------------------------------------------- This transmission (including any attachments) may contain confidential info= rmation, privileged material (including material protected by the solicitor= -client or other applicable privileges), or constitute non-public informati= on. Any use of this information by anyone other than the intended recipient= is prohibited. If you have received this transmission in error, please imm= ediately reply to the sender and delete this information from your system. = Use, dissemination, distribution, or reproduction of this transmission by u= nintended recipients is not authorized and may be unlawful.