[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bug triaging, debugging and patches
From: |
Paul Eggert |
Subject: |
Re: Bug triaging, debugging and patches |
Date: |
Mon, 28 Aug 2017 09:57:27 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0 |
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. For an
example of a bug *not* to look at, please see Bug#28213, a hairy one
involving our conservative garbage collector mistakenly reclaiming some
objects that are not actually garbage. (I'm looking at it now and
tearing my hair out.)
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
Thanks for volunteering, by the way.