From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Shakthi Kannan <author@shakthimaan.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Bug triaging, debugging and patches
Date: Wed, 30 Aug 2017 21:32:25 -0400 [thread overview]
Message-ID: <CAM-tV-8p2RrRKvxMaX57B-9gYK6rm5r5sX6x61wBbwrrZ_sjiA@mail.gmail.com> (raw)
In-Reply-To: <82d21ca1-54d7-051c-abb0-16b3d362484b@cs.ucla.edu>
On Mon, Aug 28, 2017 at 12:57 PM, Paul Eggert <eggert@cs.ucla.edu> 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
> 99999@debbugs.gnu.org.
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
admin/notes/bugtracker.
> Thanks for volunteering, by the way.
Seconded.
next prev parent reply other threads:[~2017-08-31 1:32 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
2017-08-31 1:32 ` Noam Postavsky [this message]
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=CAM-tV-8p2RrRKvxMaX57B-9gYK6rm5r5sX6x61wBbwrrZ_sjiA@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=author@shakthimaan.com \
--cc=eggert@cs.ucla.edu \
--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).