From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Joel Brobecker <brobecker@adacore.com>, gdb-patches@sourceware.org
Subject: Re: ANNOUNCEMENT: ChangeLog policy change after GDB 11
Date: Sat, 26 Jun 2021 22:42:45 -0400 [thread overview]
Message-ID: <0a45d93b-a293-0a2e-91ad-0ad88cb1747e@polymtl.ca> (raw)
In-Reply-To: <20210613151051.GA1620040@adacore.com>
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
next prev parent reply other threads:[~2021-06-27 2:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-13 15:10 Joel Brobecker
2021-06-14 1:25 ` Mike Frysinger via Gdb-patches
2021-06-14 12:26 ` Pedro Alves
2021-06-27 2:42 ` Simon Marchi via Gdb-patches [this message]
2021-06-28 17:28 ` Joel Brobecker
2021-06-28 17:41 ` Simon Marchi via Gdb-patches
2021-06-28 20:59 ` Luis Machado via Gdb-patches
2021-06-29 1:10 ` Mike Frysinger via Gdb-patches
2021-06-29 10:07 ` Hannes Domani via Gdb-patches
2021-07-02 4:50 ` Mike Frysinger via Gdb-patches
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0a45d93b-a293-0a2e-91ad-0ad88cb1747e@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=brobecker@adacore.com \
--cc=simon.marchi@polymtl.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox