From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-pg10.blackberry.com (smtp-pg10.blackberry.com [68.171.242.226]) by sourceware.org (Postfix) with ESMTPS id ACB40385040B for ; Wed, 4 Aug 2021 15:14:29 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org ACB40385040B Received: from pps.filterd (mhs400ykf.rim.net [127.0.0.1]) by mhs400ykf.rim.net (8.16.0.43/8.16.0.43) with SMTP id 174FDRIP135004; Wed, 4 Aug 2021 11:14:13 -0400 Received: from xch214cnc.rim.net (xch214cnc.rim.net [10.3.27.119]) by mhs400ykf.rim.net with ESMTP id 3a783395v1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 04 Aug 2021 11:14:13 -0400 Received: from XCH214CNC.rim.net (10.3.27.119) by XCH214CNC.rim.net (10.3.27.119) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2176.14; Wed, 4 Aug 2021 11:14:13 -0400 Received: from XCH214CNC.rim.net ([fe80::956f:2cb6:9c26:7e18]) by XCH214CNC.rim.net ([fe80::956f:2cb6:9c26:7e18%4]) with mapi id 15.01.2176.014; Wed, 4 Aug 2021 11:14:13 -0400 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: Wed, 4 Aug 2021 15:14:13 +0000 Message-ID: <9c2a6aa76dc942c98022e29b775cc7d8@blackberry.com> References: <4205d383-e98e-f591-9031-f48925634c65@polymtl.ca> <44ea4b55-6ba2-77b2-adf4-12faa2fcad9d@polymtl.ca> <9d57a0ab883243e98ae1e357200e34c6@blackberry.com> <85182cc1-d65e-1441-5435-944bf09864f7@polymtl.ca> <508a3095-6635-f030-fbe1-23454615e167@polymtl.ca> <745bb80a-2068-de05-88bb-d6ea04dea829@polymtl.ca> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [100.64.197.218] 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.391, 18.0.790 definitions=2021-08-04_03:2021-08-04, 2021-08-04 signatures=0 X-Spam-Status: No, score=-3.3 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) 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: Wed, 04 Aug 2021 15:14:31 -0000 On 2021-08-04 10:51, Simon Marchi wrote: >=20 >=20 > 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/gnul= ib.git/plain/doc/Copyright/request-assign.future__;!!COg3wY07Hnb7!-QdSDefYR= ZU83E3QoIKDECG14HQyWydyjH4yGM0yF8AikrbmXWSfBM_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 >> >=20 > Hi Stephen >=20 > Do you have any updates about this? I am still wrestling with internal demons on this, I apologise for the=20 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=20 are they a separate process? The history is very confusing. -- 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.