Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Sam James via Gdb <gdb@sourceware.org>
To: Andrew Pinski <andrew.pinski@oss.qualcomm.com>
Cc: gcc@gcc.gnu.org,  gdb@sourceware.org,  binutils@sourceware.org,
	libc-alpha@sourceware.org,  guinevere@redhat.com
Subject: Re: bugzilla keyword for beginner issues to work on
Date: Tue, 30 Sep 2025 08:49:56 +0100	[thread overview]
Message-ID: <87wm5g2xcr.fsf@gentoo.org> (raw)
In-Reply-To: <CALvbMcA+ejCeA1kZt3Bw89-9XMm0eyUz3H_J-T5PRS=JrCAw_A@mail.gmail.com>

Andrew Pinski <andrew.pinski@oss.qualcomm.com> writes:

> Hi all,
>   As talked about during the GNU tools cauldron, the gdb and gcc
> keywords usage here are different but folks mentioned it would be a
> good idea to have the same between the 2 bugzilla instances. Right now
> gcc is easyhack while gdb uses good-first-bug. Both have issues with
> the naming of each.

'good-first-*' is what people tend to search for in other
projects. Having it aligned (and optimising for new contributors) makes
sense, I think.

> [...]

sam

  parent reply	other threads:[~2025-09-30  7:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29 20:07 Andrew Pinski via Gdb
2025-09-30  6:25 ` Luis via Gdb
2025-09-30  8:08   ` Richard Biener via Gdb
2025-09-30 11:46   ` Andrew Pinski via Gdb
2025-09-30 12:08     ` Matt Rice via Gdb
2025-09-30  7:10 ` Florian Weimer via Gdb
2025-09-30  7:49 ` Sam James via Gdb [this message]
     [not found]   ` <eb1d3e79-4627-4f66-858b-e1923f9071fe@nvidia.com>
2025-09-30  9:04     ` Jonathan Wakely via Gdb
2025-09-30 11:22       ` Guinevere Larsen via Gdb
2025-09-30 11:54       ` Andrew Pinski via Gdb
2025-09-30 21:07 ` Jeff Law via Gdb

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=87wm5g2xcr.fsf@gentoo.org \
    --to=gdb@sourceware.org \
    --cc=andrew.pinski@oss.qualcomm.com \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=guinevere@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=sam@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