unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,  emacs-devel@gnu.org,  dev@rjt.dev
Subject: Re: emacs-29 1ef8b90ae06: Simplify imenu setup for {cmake, dockerfile}-ts-modes
Date: Sun, 28 Jan 2024 13:21:23 +0800	[thread overview]
Message-ID: <87jznuhw30.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkm=2aP9xnxeUknc_9S7EAv=N8B6O=CL-0cxM6G=+n4QzrA@mail.gmail.com> (Stefan Kangas's message of "Sat, 27 Jan 2024 19:00:34 -0800")

Stefan Kangas <stefankangas@gmail.com> writes:

> ? They are not affected by this change though?  Are we looking at the
> same patch (commit 1ef8b90a)?
>
> Which areas of Emacs do you think are affected?  AFAICT, nothing risks
> breaking outside of the changed modes.  For example, autoloading is not
> affected (`declare-function' only affects byte-compilation).

You are correct as to autoloads, but it certainly affects imenu.

> Did you read Bug#68706?  Yuan decided to install it as a bugfix on
> emacs-29.
>
> The question is if this change is different from the many other bug
> fixes that we routinely install without much justification.  This is why
> I'm asking for something more specific.

Yes I did: it's larger, and encompasses much more than only the fix.
Yuan's precise wording was:

> Thanks Randy, pushed to emacs-29 since it includes a fix.

which does not suggest that the safety of the patch in whole was a
factor in his decision, but only the fact that a bugfix was one
component of the patch.  This prompted my reply that the inclusion of a
bugfix is not the sole criterion we expect changes to the release branch
to satisfy, and I trust we are in agreement in this respect.

> I don't know which changes this is in reference to, but I know that you
> often work on things like X support, that carries with it a bigger risk
> for breakage (as it's more complex), and it affects more users to boot.
> It is natural to be more careful with changes in core functionality than
> in specific modes.
>
> Note also that we have been decided to be more lax when it comes to the
> treesitter stuff, seeing as its new in Emacs 29.

No disagreements there, but "the treesitter stuff" doesn't extend to
imenu setup code in major modes which happen to make use of tree-sitter.



  reply	other threads:[~2024-01-28  5:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <170633049046.30614.86278647904102476@vcs2.savannah.gnu.org>
     [not found] ` <20240127044130.C6F37C4068B@vcs2.savannah.gnu.org>
2024-01-27  4:59   ` emacs-29 1ef8b90ae06: Simplify imenu setup for {cmake, dockerfile}-ts-modes Po Lu
2024-01-27  7:35     ` Eli Zaretskii
2024-01-27  8:05       ` Po Lu
2024-01-27 22:40         ` Stefan Kangas
2024-01-28  1:34           ` Po Lu
2024-01-28  3:00             ` Stefan Kangas
2024-01-28  5:21               ` Po Lu [this message]
2024-01-28  3:29           ` Dmitry Gutov
2024-01-28  5:57           ` Eli Zaretskii
2024-01-31  6:44             ` Yuan Fu
2024-01-27  8:37   ` Po Lu

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=87jznuhw30.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=dev@rjt.dev \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=stefankangas@gmail.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).