From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Third Newsgroups: gmane.emacs.devel Subject: Re: Gitlab Migration Date: Sat, 28 Aug 2021 10:25:31 +0100 Message-ID: References: <83zgt2p0vg.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="5090"; mail-complaints-to="usenet@ciao.gmane.io" Cc: mardani29@yahoo.es, danflscr@gmail.com, Stefan Monnier , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Aug 28 11:26:38 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 1mJubl-00019w-O4 for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Aug 2021 11:26:38 +0200 Original-Received: from localhost ([::1]:33812 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mJubk-0000ZQ-ID for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Aug 2021 05:26:36 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44476) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJub2-0007rG-9f for emacs-devel@gnu.org; Sat, 28 Aug 2021 05:25:52 -0400 Original-Received: from outbound.soverin.net ([2a01:4f8:fff0:65::8:228]:42773) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mJuay-0006pY-Ea; Sat, 28 Aug 2021 05:25:51 -0400 Original-Received: from smtp.soverin.net (unknown [10.10.3.24]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by outbound.soverin.net (Postfix) with ESMTPS id 1A581292; Sat, 28 Aug 2021 09:25:37 +0000 (UTC) Original-Received: from smtp.soverin.net (smtp.soverin.net [159.69.232.138]) by soverin.net DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=idiocy.org; s=soverin; t=1630142735; bh=yE3YIDTdQDZlOvfUdZPWASWAvG2xD/JzKGzuN0suV/E=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=RyN6yqPdbwZ+S8pj1VNAvbVlIWT/3o+LPZFLDJje0VaMj7220vDx2Rj5Iy48c1A+n oFtfiLr6SoTciOfeqBGxh1CE7DvYKKxGh5HVKNbfOMUGgfJ7gRHZ6hWccfISwJzw5A xNQ2V4dBFGgEQUuF72SB0L6yAqnHaJnJm260LKkC1Gu7Uf5ZpwY7vRxqL9mltqcge9 H0orZRmx1KL4gDx53p/2wKnZNSbmi30s2Bj6vj/6I6uLoEnC5lLat+C86mVV3r5QHo vazaxUafum6I4xI2Svc+Ecjzg0o41nCcYqH9NgYKjUKPMDDrNZpler6tCGtOyrio4W eikGyq1sJUNjw== Original-Received: from alan by faroe.holly.idiocy.org with local (Exim 4.94.2) (envelope-from ) id 1mJuah-000xvc-Am; Sat, 28 Aug 2021 10:25:31 +0100 Mail-Followup-To: Alan Third , Eli Zaretskii , Stefan Monnier , emacs-devel@gnu.org, danflscr@gmail.com, mardani29@yahoo.es Content-Disposition: inline In-Reply-To: <83zgt2p0vg.fsf@gnu.org> Received-SPF: pass client-ip=2a01:4f8:fff0:65::8:228; envelope-from=alan@idiocy.org; helo=outbound.soverin.net X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:273264 Archived-At: On Sat, Aug 28, 2021 at 08:57:39AM +0300, Eli Zaretskii wrote: > > - I find it a big difficult to classify bugs. I'm not sure exactly what > > I'd like, and maybe some of it can be done via tags and other things > > already, but I think I'd like it if bugs could be "assigned" to persons > > and/or to files and/or to "subsystems", and maybe even combine this > > with ways to describe relationships between those things (so the > > search tools can known that a given file belongs to a particular > > subsystem, for example). > > We should first come up with a meaningful classification that would > help in handling the bugs. Only then we can talk about the > implementation. I don't have any practical suggestion for > classification ATM, and frankly, as long as we have only a handful of > people doing this, it doesn't sound very important. I occasionally use the usertags feature to tag bug reports as for NS, which is very helpful for finding relevant bugs. Someone else was doing it before me, and not all NS bugs are tagged. I struggle to remember how to use the email-based admin for debbugs, so I only ever tag them when I'm using the emacs debbugs UI, which is much less often than I use my MUA. Not relevant to this discussion, but it has just occurred to me that since I write all my emails in Emacs it should be possible to create some sort of system for semi-automatically inserting debbugs commands into the current email body. -- Alan Third