From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: [RFE] Migration to gitlab Date: Wed, 15 May 2019 04:30:46 +0200 Message-ID: <87a7foih49.fsf@mouse.gnus.org> References: <1552789070.5272.1@yandex.ru> <1552793646.5272.3@yandex.ru> <1552821396.21432.0@yandex.ru> <83imwhwf4x.fsf@gnu.org> <837ecvux2q.fsf@gnu.org> <9c7cf558-a2d3-951e-d6e1-31b3ad5900cf@yandex.ru> <1553064994.13109.0@yandex.ru> <831s32t3fn.fsf@gnu.org> <93f38b88-059b-b243-49bf-df61f424fb3f@yandex.ru> <83o94zap79.fsf@gnu.org> <5161ae04-391e-49d8-e942-127c04062c27@yandex.ru> <83sgu6zbfe.fsf@gnu.org> <83imv2z74u.fsf@gnu.org> <6391f225-1d4d-06ae-eef5-9f069ef6878f@yandex.ru> <83sgu5yi5p.fsf@gnu.org> <83d0l9xkbz.fsf@gnu.org> <16b894b3-fde4-02bb-eb64-096fe444c514@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="268291"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Eli Zaretskii , theophilusx@gmail.com, hi-angel@yandex.ru, emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed May 15 04:31:31 2019 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hQjhZ-0017bP-0C for ged-emacs-devel@m.gmane.org; Wed, 15 May 2019 04:31:29 +0200 Original-Received: from localhost ([127.0.0.1]:57925 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hQjhX-0007k8-Sr for ged-emacs-devel@m.gmane.org; Tue, 14 May 2019 22:31:27 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:38737) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hQjgz-0007k0-4W for emacs-devel@gnu.org; Tue, 14 May 2019 22:30:54 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hQjgx-0006en-UD for emacs-devel@gnu.org; Tue, 14 May 2019 22:30:53 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:47058) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hQjgx-0006ab-MQ; Tue, 14 May 2019 22:30:51 -0400 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=sandy) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hQjgs-0007Wb-Qm; Wed, 15 May 2019 04:30:49 +0200 In-Reply-To: <16b894b3-fde4-02bb-eb64-096fe444c514@yandex.ru> (Dmitry Gutov's message of "Sat, 27 Apr 2019 04:40:06 +0300") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 80.91.231.51 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:236531 Archived-At: Dmitry Gutov writes: > Again: > > - Searching the bug tracker for duplicates. > - Tagging the bug. > - Changing priority. > - Closing it as a duplicate, maybe. > > All of these require interacting with Debbugs. Usually through the > control server. I haven't followed this discussion closely, so I don't know whether anybody's mentioned this before: Emacs does have a way to interact with the Emacs bug tracker through the debbugs-gnu package. I don't know whether anybody else uses it to do bug triage but me, though. :-) It allows you to do all those things you mention (except searching bug report bodies) without knowing anything about debbugs syntax. It's got some problems, though: The initial time it uses to display the list of bugs is long (15 seconds), and there's no way to update the list without re-fetching the entire list, which is a bore. But the debbugs API just doesn't have any way to say "get bug reports that have changed since