emacs-devel
[Top][All Lists]
Advanced

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

Re: Gitlab Migration


From: Eli Zaretskii
Subject: Re: Gitlab Migration
Date: Sat, 28 Aug 2021 11:11:20 +0300

> From: Daniel Martín <mardani29@yahoo.es>
> Cc: danflscr@gmail.com,  emacs-devel@gnu.org
> Date: Fri, 27 Aug 2021 16:17:24 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >
> > Are you asking about contributors or about the core maintainers?
> > E.g., you mention interaction with bug reports, but AFAIK contributors
> > have only one kind of interaction here: when they submit a report.  So
> > I wonder whether I understand your questions.
> 
> The core maintainers: The people that usually check for new bug reports
> and act on them, classify them by priority and see if they block a
> release, review and commit any patches that are sent to fix the bugs,
> etc.

I do almost everything inside Emacs.  Once I've got bug report in
Emacs, as part of reading email, I use the Emacs facilities to work on
it: the code inspection features like M-. and "M-x grep", Lisp
evaluation, Help commands, etc.  I do use the debbugs package, albeit
rarely, mainly when I need to work on large numbers of bugs.

For search, I use the Debbugs Web form (but I rarely need that,
either); I also have email search set up, but that's also rarely
needed.

For code review, it is important for me to be able to do the following
basic tasks efficiently while reviewing the patch:

  . find code in Emacs
  . copy code from Emacs's sources to the review text
  . spell-check what I write and fix typos
  . run Git commands, including forensics and patch application
  . read past discussions of the same or related issues

Does this answer your question?



reply via email to

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