all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: emacs-devel@gnu.org
Subject: Re: Consequent CC Mode fix to the release branch or to master?
Date: Mon, 23 Jan 2023 18:46:50 +0200	[thread overview]
Message-ID: <83h6whi4g5.fsf@gnu.org> (raw)
In-Reply-To: <Y86vMZj7Yq0ZAYRF@ACM> (message from Alan Mackenzie on Mon, 23 Jan 2023 16:00:49 +0000)

> Date: Mon, 23 Jan 2023 16:00:49 +0000
> Cc: emacs-devel@gnu.org
> From: Alan Mackenzie <acm@muc.de>
> 
> 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?

It depends on the patch.  Please show it, so I could have an idea of
what it entails.

> 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?

I hope we will have the first pretest in a week or so.



  reply	other threads:[~2023-01-23 16:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-23 16:00 Consequent CC Mode fix to the release branch or to master? Alan Mackenzie
2023-01-23 16:46 ` Eli Zaretskii [this message]
2023-01-23 17:04   ` Alan Mackenzie
2023-01-23 17:09     ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83h6whi4g5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=acm@muc.de \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.