unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Wilhelm Kirschbaum <wkirschbaum@gmail.com>
Cc: 66183@debbugs.gnu.org, casouri@gmail.com, jm@pub.pink
Subject: bug#66183: elixir-ts-mode test failure
Date: Sat, 07 Oct 2023 12:05:01 +0300	[thread overview]
Message-ID: <837cny2476.fsf@gnu.org> (raw)
In-Reply-To: <87il7irfa3.fsf@gmail.com> (message from Wilhelm Kirschbaum on Sat, 07 Oct 2023 10:44:12 +0200)

> From: Wilhelm Kirschbaum <wkirschbaum@gmail.com>
> Cc: casouri@gmail.com, 66183@debbugs.gnu.org, jm@pub.pink
> Date: Sat, 07 Oct 2023 10:44:12 +0200
> 
> 
> 
> >> > It’s absolutely my fault :-) Several people have had 
> >> > confusion
> >> > about it, because the docstring wasn’t clear enough. I’ve 
> >> > updated
> >> > the docstring so hopefully this confusion won’t occur in the
> >> > future.
> >> 
> >> Should this doc-string fix be cherry-picked to the release 
> >> branch?
> >> 
> 
> I don't see why not, because the elixir-ts-mode patch works on 
> 29.1 as well. 

Done.





      reply	other threads:[~2023-10-07  9:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-24 16:53 bug#66183: elixir-ts-mode test failure john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-25  3:12 ` Yuan Fu
2023-09-25 16:01   ` john muhl via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-26  6:18     ` Wilhelm Kirschbaum
2023-09-26 16:30   ` Wilhelm Kirschbaum
2023-09-26 18:00     ` Yuan Fu
2023-09-26 20:26       ` Wilhelm Kirschbaum
2023-09-27  6:46         ` Yuan Fu
2023-09-27  7:17           ` Wilhelm Kirschbaum
2023-09-29 11:14       ` Eli Zaretskii
2023-10-05  7:18         ` Eli Zaretskii
2023-10-07  8:44           ` Wilhelm Kirschbaum
2023-10-07  9:05             ` Eli Zaretskii [this message]

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=837cny2476.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=66183@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=jm@pub.pink \
    --cc=wkirschbaum@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).