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: Choice of bug tracker Date: Thu, 31 Aug 2023 15:37:36 +0300 Message-ID: <83a5u7e6b3.fsf@gnu.org> References: <87il9kksqz.fsf@dfreeman.email> <831qfrptiq.fsf@gnu.org> <57429221-d9be-5791-e975-b3539905e2f6@gutov.dev> <83a5udlj47.fsf@gnu.org> <87a5udk1co.fsf@posteo.net> <835y51kslv.fsf@gnu.org> <7a82c524-1aa1-e755-e377-673ebb107a44@gutov.dev> <83r0nok8s4.fsf@gnu.org> <83ledwk4xi.fsf@gnu.org> <76ecf629-a41a-f6e4-f661-2ef926326d6c@gutov.dev> <83zg2cias7.fsf@gnu.org> <83pm37ie54.fsf@gnu.org> <831qfmhyx3.fsf@gnu.org> <87pm36kqlg.fsf@posteo.net> <87il8yuk6q.fsf@yahoo.com> <87ttsfts92.fsf@localhost> <87r0njtrdl.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28377"; mail-complaints-to="usenet@ciao.gmane.io" Cc: brickviking@gmail.com, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Aug 31 14:38:12 2023 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 1qbgw8-00079a-KP for ged-emacs-devel@m.gmane-mx.org; Thu, 31 Aug 2023 14:38:12 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qbgvt-0005nm-6O; Thu, 31 Aug 2023 08:37:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qbgvr-0005hw-Vj for emacs-devel@gnu.org; Thu, 31 Aug 2023 08:37:56 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qbgvr-0007r7-NA; Thu, 31 Aug 2023 08:37:55 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=O69WY8XLMGLdo3fBUKZWizF6Jt+4Wn4UKsMKA5DouW4=; b=DsAzwaBCr2Jn ty1n/JfcFYCi3a0FEs+tpRPFXeGirjaNNJnEVqcZ+Jk8yn2hV6ihVncsapkhAgfXPjlixDvySN9hX n11SSIaV5R15uPLcurwbcp2raJD+XzroklWc3FerXLSD54TK4vQhQaFPtH0B8ySxSFdS1eSHMoYYP kmPvIYaUxpqzTX1hhPUy7v+I3hz63/TgOFCIF8r/s20QHSuU1R8XYeF6z0mdCylLzN8pBUMhYAkVm tJhBjDcS/l/TimYGMDM9Kn6nR2ivkVGdvu2V8uAYWl83CD+jgXoEJfOAfzHx252yXndcASPQJjz0E m1jRSb7JC6VkpAxX+b2WeQ==; In-Reply-To: <87r0njtrdl.fsf@localhost> (message from Ihor Radchenko on Thu, 31 Aug 2023 10:53:26 +0000) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:309638 Archived-At: > From: Ihor Radchenko > Cc: emacs-devel@gnu.org > Date: Thu, 31 Aug 2023 10:53:26 +0000 > > brickviking writes: > > >> > I think so. I hope we will also consider the capacity for separate > >> > threads of discussion within an individual bug report a feature. > >> > >> But isn't it discouraged in debbugs? > >> ... > > What if there was a hypothetical bug report that actually had a multiple > > number of things to address, but was only being reported under the original > > "bug" that the user reported on? That'd still be a good reason to be able > > to discuss #bugnum, #bugnum-feature1, #bugnum-feature2 and so on. I'm > > assuming that this is what debbugs is "discouraging"? > > Yup. It feels "illegal" to open side discussions out of debbugs email > threads. Though, on the second thought, nothing should stop users from > branching off the thread into emacs-devel while dropping debbugs > address. Discussing several separate issues in the same bug report is discouraged because (a) it makes reference to the discussion problematic in the commit log messages, and (b) it makes the discussion larger and harder to follow, since people frequently mix several issues in a single response. So our conventions when using debbugs is to open a separate bug report for each issue.