From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Confused by y-or-n-p Date: Mon, 04 Jan 2021 13:02:15 -0500 Message-ID: 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> <83eej0bnsd.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23631"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: rms@gnu.org, juri@linkov.net, rudalics@gmx.at, stefankangas@gmail.com, larsi@gnus.org, emacs-devel@gnu.org, drew.adams@oracle.com To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 04 19:03:28 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 1kwUCW-00063e-Mj for ged-emacs-devel@m.gmane-mx.org; Mon, 04 Jan 2021 19:03:28 +0100 Original-Received: from localhost ([::1]:59890 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kwUCV-0006Sd-NW for ged-emacs-devel@m.gmane-mx.org; Mon, 04 Jan 2021 13:03:27 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43164) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kwU8q-0004Nk-TZ for emacs-devel@gnu.org; Mon, 04 Jan 2021 12:59:40 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:4568) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kwU8o-0001sc-Cz; Mon, 04 Jan 2021 12:59:39 -0500 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 544EE10025D; Mon, 4 Jan 2021 12:59:36 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 21DE11000F4; Mon, 4 Jan 2021 12:59:34 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1609783174; bh=hRboW3e0XK8twcDPExsulMrrQKQ4d4cFefnVMjhBS7k=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=a9EhivO+HOwuL72ytQcBHHVPmVvqn+w0DmKAAewaIYJOqm4yvXOqQh32+AGul+A8R p05IIfrz4YYoG0R3JhQl4rnUjL8rhT0x0SeWhP4oY7qllKIiPJUsn1qYYaMF1W+DV9 JEbtMKZyZdfQg9uhnV29Hpu5JmNY8Js1Hd6DonbCAyqUIpDmaBqdjC+jOeo7GrIDPX UqJeFXYAjSQsTBdFGMXTktVIH2WKnUs/sWEqVItYj+ZZ7L3CmJ+UUOdATriMYt7ZoT 9+yWjmd3IcmkGMM1KHYnhVOjyb2TpsuLR06qdW2/SLrkfiOkyFRwZXCupk0tPnzcCC xK5O5U6ClVIZw== Original-Received: from lechazo (lechon.iro.umontreal.ca [132.204.27.242]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 150E812041A; Mon, 4 Jan 2021 12:59:34 -0500 (EST) In-Reply-To: <83eej0bnsd.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 04 Jan 2021 19:43:46 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:262462 Archived-At: >> [ FWIW, I also think there are changes we should keep enabled only on >> `master` *until* they stop being unpopular. I'm specifically >> thinking of things like removal of obsolete features. E.g. we could >> have features obsolete since Emacs-25 removed from `master` right >> now, but with a way to get them back on-demand, and with the >> understanding that they will still be present in the Emacs-28 >> release. ] > > AFAIU, this would need a more complicated procedure for cutting > a release branch: some commits would need to be reverted on the > release branch. No, I was thinking of changing `make-obsolete` and friends so they undefine (or refrain from defining) the function/variable. They could do so by testing `emacs-version` (or some other way to detect the `master` code) along with some extra config vars (e.g. a var to force the behavior globally on way or the other or only for some functions/variables). I think this would require some finer control for variables, since it's frequent for obsolete vars to still appear in the code (in order to support code that makes use of that variable), but at least for functions it should be quite straightforward. It would definitely not require any special handling when cutting the release branch or anything like that (since, as you point out, that would be completely impractical). Stefan