From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id yMiXNmWt8WIiUAEAbAwnHQ (envelope-from ) for ; Tue, 09 Aug 2022 02:42:13 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:bcc0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id wMHJNmWt8WIkrAAA9RJhRA (envelope-from ) for ; Tue, 09 Aug 2022 02:42:13 +0200 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 683A938982 for ; Tue, 9 Aug 2022 02:42:12 +0200 (CEST) Received: from localhost ([::1]:33938 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oLDJy-0003DC-7v for larch@yhetil.org; Mon, 08 Aug 2022 20:42:10 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:51738) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oLDJC-0003D4-Vg for emacs-orgmode@gnu.org; Mon, 08 Aug 2022 20:41:23 -0400 Received: from fencepost.gnu.org ([2001:470:142:3::e]:55966) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oLDJC-0000yN-LI; Mon, 08 Aug 2022 20:41:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-Version:Date:References:In-Reply-To:Subject:To: From; bh=RO1hclACQMMacs2YisJTbfhtf4qf1aoJ68LFSNAgpKM=; b=o6CuErBMayd76q5TNw5i 5VLJrMwmWRMdrbvo0NRksdBMXDdtPkakbY4Ak/6PeC+A8DqZ0Ms9qediIyg9nOeEnZZaWAperSMEt ax6SYpdt0A/y5fwhNQky6euYP6eIZ+Hyx7zg6aGZpk2C6EZnNBUGOcT0pqO2TgMAvMhuEqmkukSmS gmnSHzIvuqPMY7wngSg8vWIRPgHRhi0WsLk0Ro3qby8BzbA9hXKy+sOdeITPXNirN4J5gyhsIj3wU MfygblG9hqxf+f36LYJBixCMKwvC+6cydkQIl/+G375txV/tmJZ9wk5fUwE790DqagUkuZbeU+O/U obv1uy8hODJFbA==; Received: from 25.64.140.77.rev.sfr.net ([77.140.64.25]:33654 helo=hal) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oLDJB-0004p5-HQ; Mon, 08 Aug 2022 20:41:22 -0400 Received: by hal (Postfix, from userid 1000) id 077901E0410; Tue, 9 Aug 2022 02:41:19 +0200 (CEST) From: Bastien To: Tim Cross Cc: Ihor Radchenko , Samuel Wales , Max Nikulin , emacs-orgmode@gnu.org Subject: Re: [PATCH] Delete some Emacs 24 compat code In-Reply-To: <86czdawew8.fsf@gmail.com> (Tim Cross's message of "Tue, 09 Aug 2022 08:12:29 +1000") Organization: GNU References: <875ykikvaz.fsf@localhost> <87sfnlk0tj.fsf@localhost> <874jzg5bg7.fsf@gnu.org> <87les9l9wv.fsf@localhost> <87pmhad9gv.fsf@gnu.org> <86czdawew8.fsf@gmail.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Date: Tue, 09 Aug 2022 02:41:18 +0200 Message-ID: <87y1vydz9t.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1660005733; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=RO1hclACQMMacs2YisJTbfhtf4qf1aoJ68LFSNAgpKM=; b=nF8jmyI1KWfaoWxLsc0QRxflk1Gm+pqnaca6CP+BchTYYEnIYtfnJb9Hk2DmqvLGx6VJ+Q 482wiHfaDxa9ZK7DjKW5omcWWDYKW4WoH3DiwYXzg45o1ynWdIHCJ9itI6wZJsU8YLYYut xH3YA+6vjU4Oz5sUANU7E3C8Pn9snJmfyIXzb6xtYTDZoVQM2joqWp9CP+7BtSqmApS8yF DccHunss16FcadXZ1o9qNlOljq9BPjRSoyJ/unZSZt5vBPZFSi2yDh1qGHQ9d1UB+UfyR/ 9orFi+uB38qDT4XIzTSBBXu335zk6KbohntJbC+raptUrdpIuzAeFEk2tU96dw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1660005733; a=rsa-sha256; cv=none; b=Ppiw8KFb2dGhsFJSTD0Vd0bSKEuSrDQS5Yh8slsi9EreVcnBH4T8btQhJFTf1cyS0KPDYG VHCYzdN33q6YQG8w5qcUQvh3t0XH32+ahwcLa6+qpmVgAyW2FOAGDFmAdDY48E1yGJgSTz Cd+MXewZo2LWt2SZWyJgA5Gp/O1fJjVE08F/Vk+btvfNm4tjUDFNOk0PjM+FWEDQdRatNS TLDIXh39RCdEZ1d065GNdncSgDcj+XvE3erfK1TQfskqEC+8pgMCq359am6M9b2oQV9sqF EvHXi9/SwEs5WCg5UYY1pKFrBeAoc+5Dy39X2gZWKSm/DVf5J+1vYw9yxylqHA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gnu.org header.s=fencepost-gnu-org header.b=o6CuErBM; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Spam-Score: -9.39 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gnu.org header.s=fencepost-gnu-org header.b=o6CuErBM; dmarc=pass (policy=none) header.from=gnu.org; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org" X-Migadu-Queue-Id: 683A938982 X-Spam-Score: -9.39 X-Migadu-Scanner: scn0.migadu.com X-TUID: yIZvF43fBl6r Hi Tim, thanks for reminding me the context. Tim Cross writes: > Therefore, I think the position should be that once an emacs version is > no longer one of the supported versions (current stable Emacs release > plus two previous major versions), there is no guarantee we will inform > the list when compatibility is lost. Yes, fully agreed. If my previous message was unclear: it is *good* to inform the list of any compatibility issue (with any Emacsen), but we cannot promise we will warn the list for every breakage as we don't test Org with Emacs <=25. > If you are running an unsupported > versions, either you should avoid updates or be prepared for breakage > without warning. When we do know a commit has broken compatibility, that > information will be relayed to the list, but we cannot guarantee we can > provide such information at the time the change is committed. Running an > unsupported versions is at your own risk. Yes, thanks for articulating this very clearly. -- Bastien