From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Gitlab Migration Date: Sat, 28 Aug 2021 11:11:20 +0300 Message-ID: <83pmtyng47.fsf@gnu.org> References: <83a6l3q99e.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30630"; mail-complaints-to="usenet@ciao.gmane.io" Cc: danflscr@gmail.com, emacs-devel@gnu.org To: Daniel =?iso-8859-1?Q?Mart=EDn?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 28 10:12:33 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mJtS5-0007m2-MP for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Aug 2021 10:12:33 +0200 Original-Received: from localhost ([::1]:35198 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mJtS3-0002Lr-Tg for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Aug 2021 04:12:31 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35388) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJtRA-0001fx-Ue for emacs-devel@gnu.org; Sat, 28 Aug 2021 04:11:36 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:56644) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mJtRA-0003Vr-M6; Sat, 28 Aug 2021 04:11:36 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4130 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJtRA-0006SC-4O; Sat, 28 Aug 2021 04:11:36 -0400 In-Reply-To: (message from Daniel =?iso-8859-1?Q?Mart=EDn?= on Fri, 27 Aug 2021 16:17:24 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:273248 Archived-At: > From: Daniel Martín > Cc: danflscr@gmail.com, emacs-devel@gnu.org > Date: Fri, 27 Aug 2021 16:17:24 +0200 > > Eli Zaretskii 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?