From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id d3OGOLwl0V/LHQAAWB0awg (envelope-from ) for ; Wed, 09 Dec 2020 14:30:04 -0500 Received: by simark.ca (Postfix, from userid 112) id DAC9D1F0A9; Wed, 9 Dec 2020 14:30:04 -0500 (EST) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=0.2 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_NONE,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 Received: from sourceware.org (unknown [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 89EC41E590 for ; Wed, 9 Dec 2020 14:30:04 -0500 (EST) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 0DCBA3850418; Wed, 9 Dec 2020 19:30:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0DCBA3850418 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1607542204; bh=kDVYIpWohc/TsNeoJGevZQxV3wH0iN0BnfmmaiJy3xU=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=XoBL8FbtINvfrt4LP+ybwifakvI7mP2u+x8ANArmohWa2huwcqh7fSEb/9ZChtYJw cxUAQlapoAbFgvfGNQTZng8abzAn8ZlxYhqGntFfvmon2QDsBCzYc5XgBy7J9birXj Flw/iuCy/l18wG1lD3s7LsNC/l1apt4lqCgJWK2g= Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id DD1183850418 for ; Wed, 9 Dec 2020 19:30:01 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org DD1183850418 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 0B9JTfOa032586 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 9 Dec 2020 14:29:46 -0500 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 0B9JTfOa032586 Received: from [10.0.0.11] (173-246-6-90.qc.cable.ebox.net [173.246.6.90]) (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 886BA1E590; Wed, 9 Dec 2020 14:29:41 -0500 (EST) Subject: Re: [PATCH 1/4] gdb: make discrete_position return optional To: "Maciej W. Rozycki" , Joel Brobecker References: <20201123162120.3778679-1-simon.marchi@efficios.com> <20201123162120.3778679-2-simon.marchi@efficios.com> <20201206053835.GC321750@adacore.com> <11f410ad-f939-5668-9566-00287a3a891d@efficios.com> <20201208030632.GF3202@adacore.com> Message-ID: <2df9aeac-be70-8704-e1c1-fd108fe50c51@polymtl.ca> Date: Wed, 9 Dec 2020 14:29:40 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Wed, 9 Dec 2020 19:29:42 +0000 X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Simon Marchi via Gdb-patches Reply-To: Simon Marchi Cc: Simon Marchi , Simon Marchi via Gdb-patches Errors-To: gdb-patches-bounces@sourceware.org Sender: "Gdb-patches" On 2020-12-08 6:41 a.m., Maciej W. Rozycki wrote: > FWIW at we have a working > instance of patchwork too that can be used to track own and other people's > submissions, which also has been recently brought up to date as far as the > engine is concerned, thanks to people using it actively for the glibc > project. They've even set up a weekly meeting recently to review patches: > . That might > be something to consider I believe for patch management. Yes, I think we should use it! But our previous experience with Patchwork is that it's a lot of work to manage patches to keep Patchwork in a good state. When you send a v2, v3, v4 of a series, it creates new patches, and someone needs to manually go set the older ones as "Superseded". And when then patches get merged, someone needs to go mark them as "Merged" so they go away. Is this how it still works? If Patchwork could do that somewhat automatically and reliably (say, by relying on same the Change-Ids as Gerrit uses), I think it would be wonderful. Last time I checked [1], the upstream project was open to receive such contributions, but of course it takes some effort to implement. [1 https://github.com/getpatchwork/patchwork/issues/327 Simon