unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dev@rjt.dev, casouri@gmail.com, mattias.engdegard@gmail.com,
	theo@thornhill.no, dmitry@gutov.dev, 64019@debbugs.gnu.org,
	schwab@linux-m68k.org, dancol@dancol.org
Subject: bug#64019: 29.0.91; Fix some tree-sitter :match regexps
Date: Sun, 30 Jul 2023 14:46:44 +0200	[thread overview]
Message-ID: <87v8e1h8i3.fsf@epfl.ch> (raw)
In-Reply-To: <83sfaqoutu.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 17 Jun 2023 13:35:43 -0400")

notfixed 64019 29.1
fixed 64019 30.1
quit

Eli Zaretskii [2023-06-17 13:35 -0400] wrote:

>> From: Basil Contovounesios <contovob@tcd.ie>
>> Cc: dev@rjt.dev,  casouri@gmail.com,  mattias.engdegard@gmail.com,
>>   theo@thornhill.no,  dmitry@gutov.dev,  64019@debbugs.gnu.org,
>>   schwab@linux-m68k.org,  dancol@dancol.org
>> Date: Sat, 17 Jun 2023 17:56:43 +0100
>> 
>> Eli Zaretskii [2023-06-17 19:34 +0300] wrote:
>> 
>> >> Fix some tree-sitter :match regexps
>> >> 95091b77f0b 2023-06-17 16:41:35 +0100
>> >> https://git.sv.gnu.org/cgit/emacs.git/commit/?id=95091b77f0b
>> >
>> > I didn't agree for this to go to emacs-29, though.  So why did it end
>> > up there?
>> 
>> Sorry, I misunderstood.  Shall I revert?
>
> Yes, please install it on master.  We can backport later, after Emacs
> 29.1 is released.

Following the wonderful news that 29.1 is released, can this be
considered for backporting?

Thanks!

-- 
Basil





  parent reply	other threads:[~2023-07-30 12:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 14:25 bug#64019: 29.0.91; Fix some tree-sitter :match regexps Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-12 14:48 ` Mattias Engdegård
2023-06-12 15:10   ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-12 15:37     ` Eli Zaretskii
2023-06-12 20:22       ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-13  2:36         ` Eli Zaretskii
2023-06-13 13:51           ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-12 16:07     ` Mattias Engdegård
2023-06-12 21:39       ` Dmitry Gutov
2023-06-13  7:47         ` Mattias Engdegård
2023-06-13 17:06           ` Dmitry Gutov
2023-06-12 21:33 ` Dmitry Gutov
2023-06-13  2:37   ` Eli Zaretskii
2023-06-13 14:08   ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-13 17:06     ` Dmitry Gutov
2023-06-15 17:17     ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-17  2:00       ` Dmitry Gutov
2023-06-17  6:48         ` Andreas Schwab
2023-06-17  8:39           ` Mattias Engdegård
2023-06-17 12:21             ` Mattias Engdegård
2023-06-17 15:44             ` Dmitry Gutov
2023-06-17 16:13               ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-17 16:34                 ` Eli Zaretskii
2023-06-17 16:56                   ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-17 17:35                     ` Eli Zaretskii
2023-06-17 19:54                       ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-30 12:46                       ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-07-30 12:59                         ` Eli Zaretskii
2023-07-30 16:04                           ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87v8e1h8i3.fsf@epfl.ch \
    --to=bug-gnu-emacs@gnu.org \
    --cc=64019@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=contovob@tcd.ie \
    --cc=dancol@dancol.org \
    --cc=dev@rjt.dev \
    --cc=dmitry@gutov.dev \
    --cc=eliz@gnu.org \
    --cc=mattias.engdegard@gmail.com \
    --cc=schwab@linux-m68k.org \
    --cc=theo@thornhill.no \
    /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).