Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Richard Biener via Gdb <gdb@sourceware.org>
To: Luis <luis.machado.foss@gmail.com>
Cc: Andrew Pinski <andrew.pinski@oss.qualcomm.com>,
	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 10:08:49 +0200	[thread overview]
Message-ID: <9F10F8B2-8121-4B7C-8047-82EC16F2853E@gmail.com> (raw)
In-Reply-To: <d7f10ac6-7369-4620-9dcc-ebb959241b71@gmail.com>



> Am 30.09.2025 um 08:27 schrieb Luis via Gcc <gcc@gcc.gnu.org>:
> 
> On 29/09/2025 21:07, Andrew Pinski wrote:
>> 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.
>> So I was thinking of a good name and came up with beginner-improvement .
>> I know this is all bikeshedding but in this case since the 2 projects
>> right now use different naming we have a good chance to come up with a
>> good name in the first place.
>> beginner-improvement has a few advantages, first it is about being a
>> beginner to the project. How long someone can be a beginner is up to
>> them; it does not need to be their first issue solving. And the idea
>> of an issue being easy is also left behind; some of them might not
>> actually be "easy" but a beginner can still solve it.
>> Plus in many cases it is not exactly a bug but rather than an
>> improvement that needs to be done so this new name removes that side
>> of things.
>> So in summary, beginner-improvement is my proposal for the new keyword.
>> Thanks,
>> Andrew Pinski
> 
> Personally I'm fine with beginner-improvement. Would we need to go hunting for the old names to do the mass updates?

I think it’s possible to rename keywords?

Richard 

  reply	other threads:[~2025-09-30  8:09 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 [this message]
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
     [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=9F10F8B2-8121-4B7C-8047-82EC16F2853E@gmail.com \
    --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=luis.machado.foss@gmail.com \
    --cc=richard.guenther@gmail.com \
    /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