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: Confused by y-or-n-p Date: Tue, 05 Jan 2021 17:03:36 +0200 Message-ID: <83pn2ja0jb.fsf@gnu.org> References: <834kkcr1eo.fsf@gnu.org> <87k0t38g1z.fsf@mail.linkov.net> <83czyvkts6.fsf@gnu.org> <87bleetirr.fsf@mail.linkov.net> <87y2hhri3n.fsf@mail.linkov.net> <83pn2tkfg8.fsf@gnu.org> <871rf7ippu.fsf@mail.linkov.net> <83a6trg6mc.fsf@gnu.org> <87im8f951f.fsf@gnus.org> <83lfdacapo.fsf@gnu.org> <83wnwsbuwp.fsf@gnu.org> <87mtxo4tph.fsf@gnus.org> <83mtxobs41.fsf@gnu.org> <877dor4x3a.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26606"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rms@gnu.org, juri@linkov.net, rudalics@gmx.at, stefankangas@gmail.com, emacs-devel@gnu.org, drew.adams@oracle.com, monnier@iro.umontreal.ca To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jan 05 16:21:40 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 1kwo9U-0006nq-J1 for ged-emacs-devel@m.gmane-mx.org; Tue, 05 Jan 2021 16:21:40 +0100 Original-Received: from localhost ([::1]:45218 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kwo9T-0006p4-LS for ged-emacs-devel@m.gmane-mx.org; Tue, 05 Jan 2021 10:21:39 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:53194) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kwo7f-0005gO-Dl for emacs-devel@gnu.org; Tue, 05 Jan 2021 10:19:47 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35340) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kwo7e-0004bh-9g; Tue, 05 Jan 2021 10:19:46 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3148 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kwns8-0000qp-Lo; Tue, 05 Jan 2021 10:03:45 -0500 In-Reply-To: <877dor4x3a.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 05 Jan 2021 09:16:57 +0100) 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:262523 Archived-At: > From: Lars Ingebrigtsen > Cc: stefankangas@gmail.com, monnier@iro.umontreal.ca, rms@gnu.org, > juri@linkov.net, rudalics@gmx.at, emacs-devel@gnu.org, > drew.adams@oracle.com > Date: Tue, 05 Jan 2021 09:16:57 +0100 > > > I don't mind that, either, but what about people who submit changes, > > but don't intend to stick around long enough to see this process > > through? Someone will have to step in and do it for them. > > I guess the person who commits the patch is the natural person to do it > then... but in my experience, things like this is almost exclusively > done by the regular developers. I have enough examples to the contrary to make me skeptical. In any case, suppose you are wrong, and the responsible person fails to do this job, do we have Plan B? Or do we allow this process to fail? If the latter, then we don't really have any guarantee that this will work, do we?