From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Lars Ingebrigtsen Newsgroups: gmane.emacs.devel Subject: Re: Towards a cleaner build Date: Sun, 09 Jun 2019 18:44:11 +0200 Message-ID: References: <83zhn6zkgf.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="212827"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: Eli Zaretskii , Stefan Monnier , Emacs developers To: Noam Postavsky Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 09 18:46:15 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 1ha0xT-000tDm-8K for ged-emacs-devel@m.gmane.org; Sun, 09 Jun 2019 18:46:15 +0200 Original-Received: from localhost ([::1]:37036 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1ha0xR-0006YP-IH for ged-emacs-devel@m.gmane.org; Sun, 09 Jun 2019 12:46:13 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55159) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1ha0vY-0006Wy-FF for emacs-devel@gnu.org; Sun, 09 Jun 2019 12:44:17 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ha0vX-0003yl-GX for emacs-devel@gnu.org; Sun, 09 Jun 2019 12:44:16 -0400 Original-Received: from quimby.gnus.org ([80.91.231.51]:40450) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ha0vX-0003y9-AI; Sun, 09 Jun 2019 12:44:15 -0400 Original-Received: from cm-84.212.202.86.getinternet.no ([84.212.202.86] helo=stories) by quimby.gnus.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1ha0vT-0004qt-Mz; Sun, 09 Jun 2019 18:44:13 +0200 Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAMFBMVEUiISExMTNbWlza29vy 8u+Xlpm+v79GSUmjo6Tq6+aurq76+vj29vT////9/vyGgodtKnEUAAAAvklEQVQ4jWO4iwMwEJC4 8haHxL29pBqFAFdI1oFLYgvplqNJXMElgVUHanCcxaVjL6WuIkbiHLLElR/2i79afP62NvL2smyI wxjugBx7o/wTm2BCKbsy601FmFGX5wLJq3++iim1/xdULT8bAPUJxKhbCt/ZChNKBZUUPAtQLL/Z 5rpy2YmYVVm3vLuQJGCexXAuRtIh0YPDXuKmC5E60EMSi4QvYaN24pLAiKg76Ebd9MUhgdVVxErc xiVxGQDQU8nJVNDCdgAAAABJRU5ErkJggg== In-Reply-To: (Noam Postavsky's message of "Sun, 9 Jun 2019 12:28:57 -0400") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 80.91.231.51 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:237355 Archived-At: Noam Postavsky writes: >> But... perhaps we could tweak `byte-compile-warnings' featurewise, too? > > But maybe do that in a separate step (i.e., after > with-suppressed-warnings lands on master). Makes sense. Or... perhaps we'd only want to allow the new symbols in `with-suppressed-warnings' while we allow the legacy symbols in `byte-compile-warnings'? Then it'd make sense to do both at the same time... -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no