From: Paul Eggert <eggert@cs.ucla.edu>
To: Shakthi Kannan <author@shakthimaan.com>
Cc: emacs-devel@gnu.org
Subject: Re: Bug triaging, debugging and patches
Date: Mon, 28 Aug 2017 09:57:27 -0700 [thread overview]
Message-ID: <82d21ca1-54d7-051c-abb0-16b3d362484b@cs.ucla.edu> (raw)
In-Reply-To: <209865546c9d60f3e889f7aec1ffb3da.squirrel@webmail.shakthimaan.com>
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
99999@debbugs.gnu.org.
Thanks for volunteering, by the way.
next prev parent reply other threads:[~2017-08-28 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 18:31 Bug triaging, debugging and patches Shakthi Kannan
2017-08-28 16:57 ` Paul Eggert [this message]
2017-08-31 1:32 ` Noam Postavsky
2017-09-05 5:46 ` Shakthi Kannan
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=82d21ca1-54d7-051c-abb0-16b3d362484b@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=author@shakthimaan.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).