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: bug#37025: 27.0.50; smime signing and encryption does not work any longer Date: Sun, 18 Aug 2019 17:23:11 +0300 Message-ID: <83o90mmu28.fsf@gnu.org> References: <87sgq27tlb.fsf@mat.ucm.es> <837e7eqxms.fsf@gnu.org> <878srqodvn.fsf@mat.ucm.es> Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="146752"; mail-complaints-to="usenet@blaine.gmane.org" Cc: emacs-devel@gnu.org To: Uwe Brauer Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Aug 18 16:23:22 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 1hzM5Z-000c0s-Rg for ged-emacs-devel@m.gmane.org; Sun, 18 Aug 2019 16:23:21 +0200 Original-Received: from localhost ([::1]:41378 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hzM5Y-0008VZ-56 for ged-emacs-devel@m.gmane.org; Sun, 18 Aug 2019 10:23:20 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54463) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1hzM5S-0008VH-1U for emacs-devel@gnu.org; Sun, 18 Aug 2019 10:23:15 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:59506) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1hzM5R-00038Z-JA; Sun, 18 Aug 2019 10:23:13 -0400 Original-Received: from [176.228.60.248] (port=3492 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1hzM5Q-0001FE-OT; Sun, 18 Aug 2019 10:23:13 -0400 In-reply-to: <878srqodvn.fsf@mat.ucm.es> (message from Uwe Brauer on Sun, 18 Aug 2019 14:29:48 +0200) 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:239436 Archived-At: > From: Uwe Brauer > Date: Sun, 18 Aug 2019 14:29:48 +0200 > > There was a second patch which checked the pgp version. However it is > not clear to me what was agreed on. So what is the general polics in > such a case. We wait for a few days (a week or two) and if no one objects, we push. > A change was introduced, which presented a bug for some use case, a > fix was not agreed or applied. > > So shouldn't that commit not be removed, at least temporally, till a fix > is agreed upon? Only if the problem is grave and very urgent. In this case, I don't think it is, and you can revert that commit locally in the meantime if it gets in your way too much.