From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Emacs project mission (was Re: "If you're still seeing problems, please reopen." [ Date: Thu, 21 Nov 2019 20:05:08 +0200 Message-ID: <83ftihxfzf.fsf@gnu.org> References: <20191117113054.49837.qmail@mail.muc.de> <87y2wexsv1.fsf@telefonica.net> <20191118175639.08d02820@jabberwock.cb.piermont.com> <874kz0pa9y.fsf@gnus.org> <87sgmjyn60.fsf@gmx.de> <875zjelte0.fsf@gnus.org> <871ru2zubp.fsf@gmx.de> <87lfsakdxp.fsf@gnus.org> <87wobuydwz.fsf@gmx.de> <87r222ix8i.fsf@gnus.org> <87tv6yveix.fsf@gmx.de> <871ru15tnx.fsf@gnus.org> <7ecb0429-a81a-ae76-77de-bdd00e3b292b@yandex.ru> <871ru1xnvs.fsf@gnus.org> <87tv6xw91o.fsf@gnus.org> <83imndxn7v.fsf@gnu.org> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="149505"; mail-complaints-to="usenet@blaine.gmane.org" Cc: ofv@wanadoo.es, rms@gnu.org, emacs-devel@gnu.org, michael.albinus@gmx.de, dgutov@yandex.ru, larsi@gnus.org, perry@piermont.com To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Nov 21 19:09:00 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.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1iXqt1-000chY-Tb for ged-emacs-devel@m.gmane.org; Thu, 21 Nov 2019 19:09:00 +0100 Original-Received: from localhost ([::1]:43388 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iXqt0-0001X5-NX for ged-emacs-devel@m.gmane.org; Thu, 21 Nov 2019 13:08:58 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44834) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iXqpF-0007cd-J4 for emacs-devel@gnu.org; Thu, 21 Nov 2019 13:05:06 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35865) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1iXqpE-0001Sd-3e; Thu, 21 Nov 2019 13:05:04 -0500 Original-Received: from [176.228.60.248] (port=1057 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1iXqp6-0006wR-KN; Thu, 21 Nov 2019 13:04:57 -0500 In-reply-to: (message from Stefan Monnier on Thu, 21 Nov 2019 10:52:31 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] 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.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:242585 Archived-At: > From: Stefan Monnier > Date: Thu, 21 Nov 2019 10:52:31 -0500 > Cc: ofv@wanadoo.es, rms@gnu.org, emacs-devel@gnu.org, michael.albinus@gmx.de, > dgutov@yandex.ru, Lars Ingebrigtsen , perry@piermont.com > > > Once again, I think we need to talk to GitLab developers about this. > > It makes no sense not to have a solution for this issue. Maybe there > > already is one, just not widely known or documented. > > I think the only thing we need is to be able to subscribe arbitrary > email addresses to an issue (instead of being limited to subscribing > users known to Gitlab). I think it's a valuable functionality in > any case. I think we need to explain to them what are our needs, and leave it up to them to suggest the technical solution. All we need is to be able to indicate the person who submitted the original report in a way that this person will be notified of any activities in the issue.