all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Po Lu <luangruo@yahoo.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: Sat, 27 Jan 2024 19:00:34 -0800	[thread overview]
Message-ID: <CADwFkm=2aP9xnxeUknc_9S7EAv=N8B6O=CL-0cxM6G=+n4QzrA@mail.gmail.com> (raw)
In-Reply-To: <87fryijl60.fsf@yahoo.com>

Po Lu <luangruo@yahoo.com> writes:

> The burden of proof is on the author of the patch, who might be the most
> qualified person to comment on tree-sitter, but certainly not imenu,
> autoloads, or other areas of Emacs no less affected by this change.

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

>> If there are any specific technical arguments for why this particular
>> change must not be installed on emacs-29, then let's hear them.  Neither
>> generalizations nor administrative arguments will cut it, I think.
>
> I haven't heard any specific technical arguments as to why this change
> is safe.

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.

> Rather, I'm the person who is frequently told that such specific
> statements regarding the safety of a large change are "famous last
> words"--which they are, all too often, so I have taken that advice to
> heart.

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.

>> The above does not necessarily reflect the official line of the project.
>
> ??? I was summarizing what I myself have been told and observed over a
> certain length of time.

Maybe I wasn't clear enough.  I didn't entirely agree with the summary,
because it was too rigid to adequately summarize what I understand to
have been our policy so far.  What's more, the way it was formulated, I
felt like it was open to the misinterpretation that it reflected some
official decision.

I hope it is more clear now what it is that I wanted to clarify.



  reply	other threads:[~2024-01-28  3:00 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 [this message]
2024-01-28  5:21               ` Po Lu
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

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

  git send-email \
    --in-reply-to='CADwFkm=2aP9xnxeUknc_9S7EAv=N8B6O=CL-0cxM6G=+n4QzrA@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=dev@rjt.dev \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.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 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.