From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jean Louis Newsgroups: gmane.emacs.devel Subject: Re: bug archiving policy Date: Sun, 6 Dec 2020 13:18:46 +0300 Message-ID: References: <20201206092641.xv5gkqcwbpc5gau7@E15-2016.optimum.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1519"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.0 (3d08634) (2020-11-07) Cc: Bastien , Boruch Baum , Emacs-Devel List To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 06 11:24:09 2020 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 1klrD7-0000Hf-L4 for ged-emacs-devel@m.gmane-mx.org; Sun, 06 Dec 2020 11:24:09 +0100 Original-Received: from localhost ([::1]:59856 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1klrD6-0001eY-A7 for ged-emacs-devel@m.gmane-mx.org; Sun, 06 Dec 2020 05:24:08 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51150) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1klrCD-000106-IX for emacs-devel@gnu.org; Sun, 06 Dec 2020 05:23:14 -0500 Original-Received: from static.rcdrun.com ([95.85.24.50]:55373) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1klrCB-0003oA-5N; Sun, 06 Dec 2020 05:23:12 -0500 Original-Received: from localhost ([::ffff:197.157.0.57]) (AUTH: PLAIN admin, TLS: TLS1.2,256bits,ECDHE_RSA_AES_256_GCM_SHA384) by static.rcdrun.com with ESMTPSA id 00000000002C0010.000000005FCCB10C.00006DFB; Sun, 06 Dec 2020 10:23:07 +0000 Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=95.85.24.50; envelope-from=bugs@gnu.support; helo=static.rcdrun.com X-Spam_score_int: 14 X-Spam_score: 1.4 X-Spam_bar: + X-Spam_report: (1.4 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_SBL_CSS=3.335, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=no 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:260413 Archived-At: * Stefan Kangas [2020-12-06 12:54]: > (Cc to Bastien.) > > Boruch Baum writes: > > > At this point, I'm still primarily asking for the specific bug to be > > unarchived so the update can be posted, but I also want to bring the > > particular incident to the members of this list for review, and also to > > bring to attention of the members of this list the constructive comments > > that eventually ensued in the prior discussion thread[2]. > > Although the org-mode maintainers do read emacs-devel and bug-gnu-emacs > with some frequency, most subscribers are not org-mode experts. > > I would therefore recommend sending org-mode patches directly to the > org-mode mailing list: emacs-orgmode@gnu.org. This makes sure it is > seen by the competent and helpful org-mode hackers. In most cases, I > don't think there is any need to also open a bug against Emacs. There is main Emacs bug tracking system and such shall accept logically bugs that also relate to Org mode. To avoid misunderstandings for people reading advises, it is maybe more useful to say "while Org mode is part of Emacs there is also separate Org bug tracking mailing list" and then to advise users there in gentle manner. This is because not everybody can find that information easily and maintainers will say that maybe Org is not part of Emacs while it is part of Emacs thus confusing mostly new users. We better not say: "This is not Emacs bug", rather "Org related bugs are better handled on Org mailing list" like you said it already.