From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id iRgHFpiMSWh+qwkAWB0awg (envelope-from ) for ; Wed, 11 Jun 2025 10:03:04 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=simark.ca; s=mail; t=1749650584; bh=Jtb5wCMRhnsMnKMe+zS77xiBqS8nxlLwq/OXWiuO1H8=; h=Date:Subject:To:References:From:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=C4fNNdu9lPOK6jcKkAq+GyCbrDSnFAT+AkKMryqAuDvcSS1Fz77KODNU2GanydaKf BCBD7pZQWInNnIwV1mPzlBN1xCGvna1RbPSU1/yCn8v9Pmas5ASHsiNG5VlbwIyrgJ RT/is8IYQe8JCkKCbtDU9BQYxwuE8J1MwuVGVrQs= Received: by simark.ca (Postfix, from userid 112) id 3B27E1E11C; Wed, 11 Jun 2025 10:03:04 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-9.1 required=5.0 tests=ARC_SIGNED,ARC_VALID,BAYES_00, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_VALIDITY_CERTIFIED,RCVD_IN_VALIDITY_RPBL, RCVD_IN_VALIDITY_SAFE autolearn=unavailable autolearn_force=no version=4.0.1 Authentication-Results: simark.ca; dkim=pass (1024-bit key; unprotected) header.d=simark.ca header.i=@simark.ca header.a=rsa-sha256 header.s=mail header.b=iKG5QUkB; dkim=pass (1024-bit key) header.d=simark.ca header.i=@simark.ca header.a=rsa-sha256 header.s=mail header.b=BG9Evrcv; dkim-atps=neutral Received: from server2.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 ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id 873BB1E089 for ; Wed, 11 Jun 2025 10:03:03 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 136893858C98 for ; Wed, 11 Jun 2025 14:03:03 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 136893858C98 Authentication-Results: sourceware.org; dkim=pass (1024-bit key, unprotected) header.d=simark.ca header.i=@simark.ca header.a=rsa-sha256 header.s=mail header.b=iKG5QUkB; dkim=pass (1024-bit key) header.d=simark.ca header.i=@simark.ca header.a=rsa-sha256 header.s=mail header.b=BG9Evrcv Received: from simark.ca (simark.ca [158.69.221.121]) by sourceware.org (Postfix) with ESMTPS id C873B3858C60 for ; Wed, 11 Jun 2025 14:01:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org C873B3858C60 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=simark.ca Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=simark.ca ARC-Filter: OpenARC Filter v1.0.0 sourceware.org C873B3858C60 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=158.69.221.121 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1749650466; cv=none; b=GRqCARFPCF4hPqj9X7DFA2dmqwpcYiZnvT1ZrxxBj/X0EnyBCQPni3ciI4ewuH3FaYqq0sHp40UBFQTxhJkE9zw++nWprYlF/y+cQXOsQSy/P52zXm4jMQPPFBAfmsPiYLVAgk4VNqyDyaG+5RMnPEaLjcWO8YsMsbrUNlI00X0= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1749650466; c=relaxed/simple; bh=Jtb5wCMRhnsMnKMe+zS77xiBqS8nxlLwq/OXWiuO1H8=; h=DKIM-Signature:DKIM-Signature:Message-ID:Date:MIME-Version: Subject:To:From; b=U/NtZ6F66FciIH3oNhqOBVVpR0tAxsXVgKzKP/e3+lRSnN8d8tjIBJqvMRFuMClQd0AKRWrkan/4fsuqWp9DGg6iMBXBo9mZSIgWo5t13wTkUa+45eHS0lYGx1pwfKpITYWCL7BHP6mxQwhnQ4PqhEM2l7uJr32evkPBZpgn0m8= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C873B3858C60 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=simark.ca; s=mail; t=1749650465; bh=Jtb5wCMRhnsMnKMe+zS77xiBqS8nxlLwq/OXWiuO1H8=; h=Date:Subject:To:References:From:In-Reply-To:From; b=iKG5QUkBp7xT83tjFn74RWuabXseJ2bFjh97Wz+RC6piwtY3BURN5zCvRvjJ3uZly HeccEnxSz2Gbtm4sC0fMukchkarag81BilU9Gw6xfpqFDr3d5A8tnQKjnqyeZ30L/Q yxMz00XQfxPV9qsMGPgUtI0tYseht8hAujep4MI0= Received: by simark.ca (Postfix, from userid 112) id D818A1E11F; Wed, 11 Jun 2025 10:01:05 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=simark.ca; s=mail; t=1749650463; bh=Jtb5wCMRhnsMnKMe+zS77xiBqS8nxlLwq/OXWiuO1H8=; h=Date:Subject:To:References:From:In-Reply-To:From; b=BG9EvrcvYQw0/YFbN8vSjMMQJ5SXD4Z945a9UC+gMC93uo3DVyFarlnGxrpOp+iZL icAXxFZx/+WwMmQs43c0ACIS+9iHkDKDlKnVOlef7DegJFk2epfXTPmvKfZKDgdltK DEiKkUzIPgToX2wua9pfprHEb76HQSmYC8FVidBE= Received: from [172.16.0.192] (192-222-132-26.qc.cable.ebox.net [192.222.132.26]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 8FE771E089; Wed, 11 Jun 2025 10:00:58 -0400 (EDT) Message-ID: Date: Wed, 11 Jun 2025 10:00:58 -0400 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH 2/2][PR GDB/32956] gdb: query inferior's filesystem for build-id debug files To: Andrew Burgess , Fabian Kilger , gdb-patches@sourceware.org References: <20250511150113.3163767-1-kilger@sec.in.tum.de> <20250511150113.3163767-3-kilger@sec.in.tum.de> <877c27i3zb.fsf@redhat.com> <7cdc3a53-8d09-445f-a017-29084769fb76@sec.in.tum.de> <87ecvshshw.fsf@redhat.com> <85608652-8d05-436b-b099-9ea72247079d@sec.in.tum.de> <875xh2iptj.fsf@redhat.com> Content-Language: fr From: Simon Marchi In-Reply-To: <875xh2iptj.fsf@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.30 Precedence: list List-Id: Gdb-patches mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: gdb-patches-bounces~public-inbox=simark.ca@sourceware.org On 6/11/25 5:35 AM, Andrew Burgess wrote: > Fabian Kilger writes: > >> No problem, thanks for getting back to me. As a first-time contributor >> I'm a bit confused about the rules regarding merging and pushing. >> According to gdb/MAINTAINERS, I should not have write access and need to >> be first added, correct? And according to >> https://sourceware.org/gdb/wiki/ContributionChecklist >> a moderator or maintainer needs to send me a form regarding FSF >> copyright assignment first. >> >> I would appreciate some clarifications/instructions on what to do >> next. > > Unless those forms are stored somewhere that I'm not aware of, then I > don't believe I have access to them, hopefully a maintainer that does > can share them with you. I usually just link to the gnulib repo here (don't know why they are stored there, but they are): https://gitweb.git.savannah.gnu.org/gitweb/?p=gnulib.git;a=blob;f=doc/Copyright/request-assign.future;hb=HEAD It contains instructions on what to do, so the contributor can send it directly to the FSF. Simon