From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id aaqmGMDl12BFYQAAWB0awg (envelope-from ) for ; Sat, 26 Jun 2021 22:43:12 -0400 Received: by simark.ca (Postfix, from userid 112) id 5CCC21F1F2; Sat, 26 Jun 2021 22:43:12 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-0.7 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,RDNS_DYNAMIC,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (ip-8-43-85-97.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 AFA601E01F for ; Sat, 26 Jun 2021 22:43:11 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 5CFE5386483F for ; Sun, 27 Jun 2021 02:43:11 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 5CFE5386483F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1624761791; bh=phfhnNlLJ0Km/+zeKQ0uGcRPEGVvngVYqBIXHiN4mKY=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=af6vjUGXCweAC6t6CwXL8+3/RBCFWBt0yGlu2eFYrWR6Cd7wBFeBOHqoCDyRhptxW vfZYgPECUS69B3MM4IUjAyl8tI56vyqhQ4GiRapLdG2aDp5S8AWPtFNdpKkD0+4Xna 7NKbRAnFggQRInQunLta9/zlYwhiEQogS2kBV7F4= Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id B5EF0385503E for ; Sun, 27 Jun 2021 02:42:51 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org B5EF0385503E 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 15R2gjJT011268 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 26 Jun 2021 22:42:50 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 15R2gjJT011268 Received: from [10.0.0.11] (192-222-157-6.qc.cable.ebox.net [192.222.157.6]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 4E4011E01F; Sat, 26 Jun 2021 22:42:45 -0400 (EDT) Subject: Re: ANNOUNCEMENT: ChangeLog policy change after GDB 11 To: Joel Brobecker , gdb-patches@sourceware.org References: <20210613151051.GA1620040@adacore.com> Message-ID: <0a45d93b-a293-0a2e-91ad-0ad88cb1747e@polymtl.ca> Date: Sat, 26 Jun 2021 22:42:45 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: <20210613151051.GA1620040@adacore.com> 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 Sun, 27 Jun 2021 02:42:45 +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 Errors-To: gdb-patches-bounces+public-inbox=simark.ca@sourceware.org Sender: "Gdb-patches" On 2021-06-13 11:10 a.m., Joel Brobecker wrote: > - For patches with multiple authors, we ask that commits with > multiple authors have a... > > Co-Authored-By: xxx > > ... git-trailer, so that complete author information be kept. Similar to that, I was wondering if we should define a standard method to refer to a bug/PR number in a git trailer. For example, for a commit fixing an issue: Fixes: PR gdb/1234 Sometimes, you make a commit that is related to a PR but does not fix it (for example, add a KFAIL-ed test). In that case, it should be something else than "Fixes". What do people use normally for thse things? Is it necessary, or just mentioning "PR gdb/1234" somewhere in the commit message's free text will be enough to automatically link the commit to the PR? Simon