From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id bvu/Chw59WiTMj8AWB0awg (envelope-from ) for ; Sun, 19 Oct 2025 15:16:44 -0400 Authentication-Results: simark.ca; dkim=pass (2048-bit key; unprotected) header.d=jeremybryant.net header.i=@jeremybryant.net header.a=rsa-sha256 header.s=key1 header.b=eIV0Vj6y; dkim-atps=neutral Received: by simark.ca (Postfix, from userid 112) id 1F4241E047; Sun, 19 Oct 2025 15:16:44 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 4.0.1 (2024-03-25) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-2.4 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_BLOCKED, RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED autolearn=ham autolearn_force=no version=4.0.1 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 2B4AD1E047 for ; Sun, 19 Oct 2025 15:16:43 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id A3C4B3858C54 for ; Sun, 19 Oct 2025 19:16:42 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org A3C4B3858C54 Authentication-Results: sourceware.org; dkim=pass (2048-bit key, unprotected) header.d=jeremybryant.net header.i=@jeremybryant.net header.a=rsa-sha256 header.s=key1 header.b=eIV0Vj6y Received: from out-180.mta0.migadu.com (out-180.mta0.migadu.com [IPv6:2001:41d0:1004:224b::b4]) by sourceware.org (Postfix) with ESMTPS id 972083858D26 for ; Sun, 19 Oct 2025 19:16:10 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 972083858D26 Authentication-Results: sourceware.org; dmarc=pass (p=quarantine dis=none) header.from=jeremybryant.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=jeremybryant.net ARC-Filter: OpenARC Filter v1.0.0 sourceware.org 972083858D26 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=2001:41d0:1004:224b::b4 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1760901370; cv=none; b=DrgjYYnneMWOGF7PuQ71k56Ex1BciEKItEzIcIrrWZGxCKJhMFuCCCROWXnHBWz7lx0EiCqEvfl4JMjUYm4eXJ4HrVWVzreu39EBJOedWGRAWyA1hyjHpLwfjgFWswHGTDA56T2ePuV6f2elcOPspN44GxG5qV5P3vy9Fnb/G0s= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1760901370; c=relaxed/simple; bh=ipPSXX+Wk7lndy52wbRil5nrerLbCqD+ATb05vCahFs=; h=DKIM-Signature:From:To:Subject:Date:Message-ID:MIME-Version; b=h8pqmWUtB8P9niarOfkE2acWUdLg3SG9rLXrWe6dq+1zV2lgM1IodPyGo/xeNuq/tbBE5KGedPVEnV6jsKKTV1+YnUjwW6wlNoU72JCiyIy8Ue/4c6TjnWIakKo5Bj4mOLLXW7P0dC6AxJMhqwZKN3tWxiW2EDuBdxgrsJyef/o= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 972083858D26 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jeremybryant.net; s=key1; t=1760901368; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=YChrpm5nO3o5zrIdWMl6YHLMGS9BswRsZsEbubNzL/E=; b=eIV0Vj6y8hwVMeYVl7Ziu3zMaA52C7wpoZAjM+XUJ8ePBUWK6FKyjPUkmaOJeHaVS5Rzx4 Qw59UQIG2YGTvRdQrYAtQ7r5ghJxLw0675gfvl6KesgKK8AqAWn+rJyKpB36dZE/WMxLR1 uWu+hgjEGdZhIuk10ZthqANDAUncbjFzQy4Au8NWEPphA9VgTfD2e0v3HALJeV3wUmpTWr XU9WWOgPRnsMee+2DXNqWahUk/q034EksZ2T5bVSidMBny5xmWIoOtkDkyf6wRfaVYt5m/ fFghiTEDG85AdNFp90JwIPiqL6h71EptSRNVL5NQy/3XsHfT5yaSA3XzFkXtug== From: Jeremy Bryant To: Eli Zaretskii Cc: tom@tromey.com, gdb-patches@sourceware.org Subject: Contributor guidelines - Re: Ready for Write After Approval - Re: [PATCH v2] - Adapt to Python-3 print syntax In-Reply-To: <861pn1hirt.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 17 Oct 2025 14:25:42 +0300") References: <87frbl8724.fsf@jeremybryant.net> <87jz0wth2c.fsf@tromey.com> <874irz9aui.fsf@jeremybryant.net> <87plansy7o.fsf@tromey.com> <87frbik3zr.fsf@jeremybryant.net> <861pn1hirt.fsf@gnu.org> Date: Sun, 19 Oct 2025 20:16:06 +0100 Message-ID: <874iruk8i1.fsf@jeremybryant.net> MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Flow: FLOW_OUT 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 Eli Zaretskii writes: >> > Looks good, thank you. >> > Approved-By: Tom Tromey >> > >> > Tom >> >> Thanks Tom. >> >> I see the patch is not yet committed. >> >> Would someone on the "Write After Approval" list please commit the >> patch? > > I think you expect too much from the GDB maintenance processes. One > day is nowhere near enough to ping about approved-but-not-committed > changes. Eli, bringing back the second-part, truncated, of my message:- " PS: I'm not sure about the etiquette for following-up but presumably it's soon after approval so the patch is still applicable to master. The guidance here says one week for patch review only https://sourceware.org/gdb/wiki/ContributionChecklist " Perhaps my request wasn't worded properly. What is a typical wait time that is appropriate? To edit the file at https://sourceware.org/gdb/wiki/ContributionChecklist, do we submit ideas or patches here or in some other way?