From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 9/jrDzs/I2R+bBwAWB0awg (envelope-from ) for ; Tue, 28 Mar 2023 15:25:47 -0400 Received: by simark.ca (Postfix, from userid 112) id 3439B1E4A3; Tue, 28 Mar 2023 15:25:47 -0400 (EDT) Authentication-Results: simark.ca; dkim=pass (1024-bit key; secure) header.d=sourceware.org header.i=@sourceware.org header.a=rsa-sha256 header.s=default header.b=jELl16D7; dkim-atps=neutral X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-6.3 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_MED,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.6 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id C50921E110 for ; Tue, 28 Mar 2023 15:25:46 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 215023857BB2 for ; Tue, 28 Mar 2023 19:25:46 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 215023857BB2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1680031546; bh=GgePJadHpce3M7Blr6XiKhWj+7MKxUDLQaWs/zLRtlA=; h=Date:Subject:To:References:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=jELl16D7qc7oTKJkTZwY4lQ0omyIVwpc2BgKkk9Y6tqKd49J1r9TlpI0EhTgxI1L/ vCmvfURdCTWzmvYxpbaKdkQQ6qlzJfWDXkhvZIMpxXXsdEREN5yXmOyRV/UzqtwtXf DNXGc/8OOEpxxGWhg3Rh3tjO+3v9GE5YA+SxT9fQ= Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id B295D3858C5F for ; Tue, 28 Mar 2023 19:25:18 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org B295D3858C5F Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id 32SJOxZa018677 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 28 Mar 2023 15:25:03 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 32SJOxZa018677 Received: from [172.16.0.192] (192-222-143-198.qc.cable.ebox.net [192.222.143.198]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 0DDDB1E110; Tue, 28 Mar 2023 15:24:59 -0400 (EDT) Message-ID: <68acdee2-332c-1f05-699b-bba9bc9103db@polymtl.ca> Date: Tue, 28 Mar 2023 15:24:58 -0400 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.0 Subject: Re: Proposal to Removal of QNX Neutrino support from GDB Content-Language: fr To: Stephen Webb , "gdb@sourceware.org" 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> <9c2a6aa76dc942c98022e29b775cc7d8@blackberry.com> In-Reply-To: <9c2a6aa76dc942c98022e29b775cc7d8@blackberry.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Tue, 28 Mar 2023 19:24:59 +0000 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: , From: Simon Marchi via Gdb Reply-To: Simon Marchi Errors-To: gdb-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb" 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