From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Consequent CC Mode fix to the release branch or to master? Date: Mon, 23 Jan 2023 16:00:49 +0000 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30559"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Jan 23 17:01:57 2023 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 1pJzGe-0007lV-MS for ged-emacs-devel@m.gmane-mx.org; Mon, 23 Jan 2023 17:01:56 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pJzFw-0002pP-7p; Mon, 23 Jan 2023 11:01:12 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pJzFu-0002pF-Bi for emacs-devel@gnu.org; Mon, 23 Jan 2023 11:01:10 -0500 Original-Received: from mx3.muc.de ([193.149.48.5]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pJzFq-0007re-UL for emacs-devel@gnu.org; Mon, 23 Jan 2023 11:01:10 -0500 Original-Received: (qmail 46985 invoked by uid 3782); 23 Jan 2023 17:00:51 +0100 Original-Received: from acm.muc.de (p4fe15ef6.dip0.t-ipconnect.de [79.225.94.246]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Mon, 23 Jan 2023 17:00:51 +0100 Original-Received: (qmail 5705 invoked by uid 1000); 23 Jan 2023 16:00:49 -0000 Content-Disposition: inline X-Submission-Agent: TMDA/1.3.x (Ph3nix) X-Primary-Address: acm@muc.de Received-SPF: pass client-ip=193.149.48.5; envelope-from=acm@muc.de; helo=mx3.muc.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, 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.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:302613 Archived-At: Hello, Eli. Whilst fixing bug #59234 (Inappropriate fontification as a type of function call NSRectFill), I came across inappropriate handling of whitespace which leads to the Lisp error "Invalid search bound (wrong side of point)". This error is likely to occur only rarely, and probably not in the more used CC Mode modes such as C and C++. I now have a patch to fix this. Is it still OK to commit such patches to the release branch, or would it be preferred to commit it to master? I also have the actual fix to the above mentioned bug, #59234, which I intend to commit to the release branch, and one other open bug (an offshoot from bug #58883) which doesn't yet have a completed patch. Do you have firm ideas, yet, of when you're going to start the pretest cycle, such that non-pressing bugs would no longer be wanted in the release branch? Thanks! -- Alan Mackenzie (Nuremberg, Germany).