Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: ANNOUNCEMENT: ChangeLog policy change after GDB 11
Date: Mon, 28 Jun 2021 13:41:55 -0400	[thread overview]
Message-ID: <c0997ade-667d-bfb8-971e-b4b486fb476f@polymtl.ca> (raw)
In-Reply-To: <20210628172816.GC550682@adacore.com>

On 2021-06-28 1:28 p.m., Joel Brobecker wrote:
> What about...
> 
>     Bug: PR gdb/1234
> 
> ... or...
> 
>     Xref: PR gdb/1234
> 
> ?

Regardless of the name of the trailer we choose, what if we put the URL
as the value:

  Fixes: https://sourceware.org/bugzilla/show_bug.cgi?id=1234

That makes it clickable, so it's much easier to go consult it.  If, for
some reason, the bugzilla URL changed, the bug number is still in the
URL, so we don't lose anything doing so.  We just lose the "component"
part, "gdb" in your example.  But I don't think it's important to have
it here in the commit message, it doesn't really give important
information.

Simon

  reply	other threads:[~2021-06-28 17:48 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
2021-06-28 17:28   ` Joel Brobecker
2021-06-28 17:41     ` Simon Marchi via Gdb-patches [this message]
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=c0997ade-667d-bfb8-971e-b4b486fb476f@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