Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hannes Domani via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@polymtl.ca>,
	Mike Frysinger <vapier@gentoo.org>
Cc: Joel Brobecker <brobecker@adacore.com>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: ANNOUNCEMENT: ChangeLog policy change after GDB 11
Date: Tue, 29 Jun 2021 10:07:09 +0000 (UTC)	[thread overview]
Message-ID: <1285750350.40395.1624961229935@mail.yahoo.com> (raw)
In-Reply-To: <YNpzGWTZi7fJRvKQ@vapier>

 Am Dienstag, 29. Juni 2021, 03:11:19 MESZ hat Mike Frysinger via Gdb-patches <gdb-patches@sourceware.org> Folgendes geschrieben:

> On 28 Jun 2021 13:41, Simon Marchi via Gdb-patches wrote:
>
> > 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
>
>
> can we finally get shortlink redirects ?
>   https://sourceware.org/bugzilla/1234
>   https://sourceware.org/PR1234

Doesn't the second one work for you? It does for me.


Hannes

  reply	other threads:[~2021-06-29 10:07 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
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 [this message]
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=1285750350.40395.1624961229935@mail.yahoo.com \
    --to=gdb-patches@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=simon.marchi@polymtl.ca \
    --cc=ssbssa@yahoo.de \
    --cc=vapier@gentoo.org \
    /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