From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Noam Postavsky Newsgroups: gmane.emacs.devel Subject: Re: Towards a cleaner build Date: Sun, 9 Jun 2019 12:28:57 -0400 Message-ID: References: <83zhn6zkgf.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="142887"; mail-complaints-to="usenet@blaine.gmane.org" Cc: Eli Zaretskii , Stefan Monnier , Emacs developers To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 09 18:29:25 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 1ha0hA-000b39-FF for ged-emacs-devel@m.gmane.org; Sun, 09 Jun 2019 18:29:24 +0200 Original-Received: from localhost ([::1]:36982 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1ha0h7-00007s-Ud for ged-emacs-devel@m.gmane.org; Sun, 09 Jun 2019 12:29:21 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51960) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1ha0h3-00007l-8c for emacs-devel@gnu.org; Sun, 09 Jun 2019 12:29:18 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ha0h2-0002Zd-CU for emacs-devel@gnu.org; Sun, 09 Jun 2019 12:29:17 -0400 Original-Received: from mail-ot1-x32d.google.com ([2607:f8b0:4864:20::32d]:35780) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ha0h0-0002YG-O4; Sun, 09 Jun 2019 12:29:14 -0400 Original-Received: by mail-ot1-x32d.google.com with SMTP id j19so6215347otq.2; Sun, 09 Jun 2019 09:29:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NYjPUVO7kZFMDIyCB6XpDuHmgn95NMfOjpyQm1d45HM=; b=WrkZ17ERMwERtUaao4Rg34NpGFZyrS+mPzuysNKoUat8YFqdVNfdntpk0khXXP0uhE nZcSDdJXVdoDvqtLZJPXrNhM22JPsFP4t/xWHwWP06aBb1hOeNd54Pp2EI0y6f8xFzuL ouLfuviKmEWfI0iNvJpvNb5X2eOrinYz3uHErpLlGjGWENSThGQhKGYJFIWHJHz06ZNS w3Cvp17ApKFYE9BnfyxPJ1f588fXbxChrruBVGchsVZZ6thoUJS3PqvgKOsTQ06tYbSk KU3bD85mYu2QtOikG2YmY9SpCk9omrzhKlDVjw8ff4UDkEqmYRc5bbFGUjVHEZAZEfAk UkLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NYjPUVO7kZFMDIyCB6XpDuHmgn95NMfOjpyQm1d45HM=; b=Iv/VlAKWhZdYhnskzrEdBgXvcfD2CccZYoj9FxyMQY1CZoPFcxmRxZ7Ra6rLaU2yND YDx4tB5cuHG2RuQcNB/EWXxspo5xSl3FBmj2Da0cjkUQWo6OgeykOeN61No9wx10I3P7 D+yOuf7nU7jQzkHjHVGZjgKdM6w7yQCLx00xLjdUn6T23IFC/04ffhV/z5Ukps1MV/o8 N9qoysN3KepPOggCtxz6GJp6DOOLARm3VHXoX5R8P8EIg/X6OqHLRnR90zgAH3duVVxB 6mtPKe1Lb6Z00Py0IsiyJr15+q/n6T9X7N8a9Es8EQxTNkdIuP5uu0pqvHZwLNTZbRdm AEVA== X-Gm-Message-State: APjAAAUHYzEFBwQxp6IVpnouVaU71MDj8L+UwBw3F4wQi4ylSXEAPIWX dGcEPbZPljpMQrl4S7Z6E6Jb3vHCsRIW3LbgQs4= X-Google-Smtp-Source: APXvYqyRyOBtuHxFAaxHx4IZaTZFQy7Ibr2Ag4BB9fSXZppZIXBb54lFK9pOVZOMxuunAJP5/liemQ3V22PpcYDMvGA= X-Received: by 2002:a9d:6007:: with SMTP id h7mr25655271otj.368.1560097753973; Sun, 09 Jun 2019 09:29:13 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2607:f8b0:4864:20::32d 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:237352 Archived-At: On Sun, 9 Jun 2019 at 12:25, Lars Ingebrigtsen wrote: > I agree with all these, but I thought it might be nice to have the same > symbols as in byte-compile-warnings (and byte-compile-warning-types), Oh, I missed that, yeah, that make sense. > 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).