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: Merging native-comp and pgtk Date: Sat, 13 Feb 2021 11:39:45 +0200 Message-ID: <8335y0e272.fsf@gnu.org> References: <07D5E64D-DAD0-45B3-B272-627A73D7CBAE@gmail.com> <87pn1erewq.fsf@gmail.com> <87wnvlecrw.fsf@gnus.org> <83sg69o3av.fsf@gnu.org> <87mtwhctte.fsf@gnus.org> <459A0475-E3E7-4159-82DF-93809CCF1E24@gmail.com> <87eehng52n.fsf@gnus.org> <87mtwbye5b.fsf@gmail.com> <87czx7ycva.fsf@tcd.ie> <87eehmyalr.fsf@gmail.com> <877dneoewi.fsf@tcd.ie> <875z2yy6z7.fsf@gmail.com> <878s7twq2t.fsf@gmail.com> <84adc238-c424-bb6b-da28-c4232172da5b@gmx.at> <83wnvddtgh.fsf@gnu.org> <86k0rc2a44.fsf@gmail.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6915"; mail-complaints-to="usenet@ciao.gmane.io" Cc: andrewjmoreton@gmail.com, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Feb 13 10:41:23 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 1lArQZ-0001iF-I9 for ged-emacs-devel@m.gmane-mx.org; Sat, 13 Feb 2021 10:41:23 +0100 Original-Received: from localhost ([::1]:39126 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lArQY-0005bm-LX for ged-emacs-devel@m.gmane-mx.org; Sat, 13 Feb 2021 04:41:22 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40838) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1lArP9-0004s6-KL for emacs-devel@gnu.org; Sat, 13 Feb 2021 04:39:55 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46057) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1lArP9-0007ou-4P; Sat, 13 Feb 2021 04:39:55 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4222 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1lArP3-0008Ma-5p; Sat, 13 Feb 2021 04:39:54 -0500 In-Reply-To: (message from Stefan Monnier on Fri, 12 Feb 2021 18:06:45 -0500) 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:264587 Archived-At: > From: Stefan Monnier > Date: Fri, 12 Feb 2021 18:06:45 -0500 > Cc: emacs-devel@gnu.org > > > For me, the native-comp branch is not yet usable on mingw64 64bit: > > Should "usable on mingw64" a prerequisite to merge a branch for an > experimental feature that will only be activated upon explicit > user request? We may indeed decide that good support for the MS-Windows build is not a prerequisite, but then we'd need someone to volunteer to fix any potential problems, including breaking the MS-Windows build, as result of the merge. IME, any breakage of that kind on master is left unfixed until yours truly does it. If I'm unable to build the native-comp code (and Andy just said the --with-wide-int configuration, which is what I use, doesn't build), then I will be unable to build and test this code, and will not be able to fix any problems reported for master, whether on MS-Windows or on other platforms. Then someone else will have to take over that job. IOW, having a master branch that one of the co-maintainers cannot build is not a good situation. We should try avoiding it, IMO.