[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug triaging, debugging and patches

From: Noam Postavsky
Subject: Re: Bug triaging, debugging and patches
Date: Wed, 30 Aug 2017 21:32:25 -0400

On Mon, Aug 28, 2017 at 12:57 PM, Paul Eggert <address@hidden> wrote:
> On 08/26/2017 11:31 AM, Shakthi Kannan wrote:
>> Is there a group or subsystem of bugs that do not yet require a large  >
>> understanding of the code base that I can get started with? I am
> happy > to explore source code, if required.
> Perhaps you can start with bugs labeled "wishlist" or "minor" in the main
> listing:
> https://debbugs.gnu.org/cgi/pkgreport.cgi?package=emacs
> Please use your best judgment as to how much code-base understanding is
> required, as we don't specifically classify bug reports that way.

Actually, I've tagged a handful of bugs as "easy", you can see a list
at https://debbugs.gnu.org/cgi/pkgreport.cgi?include=tags%3Aeasy;package=emacs

Alternatively, just reporting if you can reproduce any existing bug is
useful, and shouldn't require any specific knowledge of the code.

>> If you can also shed some light on specific configurations and
>> workflows to work with the Emacs bugs database, I can set it up
>> accordingly.
> I suggest using 'git format-patch' and/or 'git send-email' to propose a fix
> for a particular bug. For Bug#99999, you can send email to
> address@hidden

You might also want to checkout the debuggs.el ELPA package
http://elpa.gnu.org/packages/debbugs.html, you can use it to browse
the bug database from within Emacs. For example, to get the listing of
"easy" bugs I linked above, M-x debbugs-gnu-search RET RET package RET
emacs RET tag RET easy RET RET. And assuming you have email setup, you
can manipulate bugs as well. See admin/notes/bug-triage and

> Thanks for volunteering, by the way.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]