From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 5xnUFN+JPmR7eS8AWB0awg (envelope-from ) for ; Tue, 18 Apr 2023 08:15:27 -0400 Received: by simark.ca (Postfix, from userid 112) id 42B851E221; Tue, 18 Apr 2023 08:15:27 -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=StlZr2Qn; 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=-9.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_HI,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 E8F801E0D3 for ; Tue, 18 Apr 2023 08:15:26 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 1A8A0385843A for ; Tue, 18 Apr 2023 12:15:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1A8A0385843A DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1681820125; bh=uaHm8HnrtkLT4FYWlrzAS0grj3zIMJpsqyRWGxVMJQg=; h=Date:Subject:To:References:Cc:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From:Reply-To:From; b=StlZr2QnLjAHRCULgwG/k1qURRTXZeiJkhAvp0vC/xIYPqw4gW6jSSW5baLgE65e3 GGoYBZrQnbfB01HidUKuRb8u+UIMSCHQZ2+sM4YI5uMvphEyHqjTThLjnh4QdRND17 DbH2Znyd0bmpcK965XI8efKO9WcPQQxpdgK5BUMk= Received: from smtp-out1.suse.de (smtp-out1.suse.de [195.135.220.28]) by sourceware.org (Postfix) with ESMTPS id A0D743853D0A for ; Tue, 18 Apr 2023 12:15:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org A0D743853D0A Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id D692D21A3C; Tue, 18 Apr 2023 12:15:05 +0000 (UTC) Received: from imap2.suse-dmz.suse.de (imap2.suse-dmz.suse.de [192.168.254.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-521) server-digest SHA512) (No client certificate requested) by imap2.suse-dmz.suse.de (Postfix) with ESMTPS id C243F13581; Tue, 18 Apr 2023 12:15:05 +0000 (UTC) Received: from dovecot-director2.suse.de ([192.168.254.65]) by imap2.suse-dmz.suse.de with ESMTPSA id oQwmLsmJPmS/CwAAMHmgww (envelope-from ); Tue, 18 Apr 2023 12:15:05 +0000 Message-ID: <1a4148e1-1376-3bc6-e398-4c611922c58f@suse.de> Date: Tue, 18 Apr 2023 14:15:06 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.9.1 Subject: Re: [PATCH v3] gdb: Fix false match issue in skip_prologue_using_linetable Content-Language: en-US To: gdb-patches@sourceware.org References: <20230418120939.29102-1-tdevries@suse.de> Cc: WANG Rui In-Reply-To: <20230418120939.29102-1-tdevries@suse.de> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit 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: Tom de Vries via Gdb-patches Reply-To: Tom de Vries Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 4/18/23 14:09, Tom de Vries via Gdb-patches wrote: > Co-Authored-By: WANG Rui (fix, tiny change [1]) > Co-Authored-By: Tom de Vries (test-case) > > [1] https://www.gnu.org/prep/maintain/html_node/Legally-Significant.html Hi, I'm not used to deal with these matters, so I'd appreciate some review/approval on this. Is my copyright status assessment correct, and did I write it up correctly? Thanks, - Tom