From: Prateek Sharma <ps.prateek.sharma143@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Yuan Fu <casouri@gmail.com>, 70478@debbugs.gnu.org
Subject: bug#70478: 30.0.50; [PATCH] Fix treesitter-font-lock-settings for built-in functions and attributes.
Date: Wed, 24 Apr 2024 19:16:08 +0530 [thread overview]
Message-ID: <CALFrjHzN=AA5fxYp3quCejvdvgraxCsmHTfHouZPcjJSJ09HrQ@mail.gmail.com> (raw)
In-Reply-To: <86r0ew4ndg.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
Hi Eli,
When do we merge emacs-29 to master? I noticed that the changes are not
merged in master. Do we have a schedule for syncing master with emacs-29?
On Tue, Apr 23, 2024 at 11:44 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Yuan Fu <casouri@gmail.com>
> > Date: Mon, 22 Apr 2024 21:26:06 -0700
> > Cc: Prateek Sharma <ps.prateek.sharma143@gmail.com>,
> > 70478@debbugs.gnu.org
> >
> > > On Apr 22, 2024, at 9:21 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > >
> > > No need to revert, as the patch was quite small, AFAIR, below the
> threshold.
> >
> > Oh right. Somehow I thought the patch are larger than it actually it.
> False alarm!
>
> Well, the commit log message should have had the
> "Copyright-paperwork-exempt" cookie, but given that the paperwork is
> in the works, this is not a grave problem.
>
[-- Attachment #2: Type: text/html, Size: 1447 bytes --]
next prev parent reply other threads:[~2024-04-24 13:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 21:00 bug#70478: 30.0.50; [PATCH] Fix treesitter-font-lock-settings for built-in functions and attributes Prateek Sharma
2024-04-20 6:13 ` Eli Zaretskii
2024-04-20 6:54 ` Prateek Sharma
2024-04-20 6:55 ` Prateek Sharma
2024-04-20 7:41 ` Eli Zaretskii
2024-04-20 7:53 ` Prateek Sharma
2024-04-21 3:47 ` Yuan Fu
2024-04-21 5:16 ` Prateek Sharma
2024-04-21 5:27 ` Eli Zaretskii
2024-04-21 23:39 ` Yuan Fu
2024-04-22 2:29 ` Prateek Sharma
2024-04-22 6:36 ` Yuan Fu
[not found] ` <CALFrjHxRZyriFw4cS-hQWZbbVbf5otnP6qGqZAY42z=Tf648Nw@mail.gmail.com>
2024-04-22 15:50 ` Yuan Fu
2024-04-22 16:18 ` Prateek Sharma
2024-04-22 16:21 ` Eli Zaretskii
2024-04-23 4:26 ` Yuan Fu
2024-04-23 6:14 ` Eli Zaretskii
2024-04-24 13:46 ` Prateek Sharma [this message]
2024-04-24 15:31 ` Eli Zaretskii
2024-04-24 15:33 ` Prateek Sharma
2024-04-22 6:28 ` Eli Zaretskii
2024-04-22 6:34 ` Yuan Fu
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='CALFrjHzN=AA5fxYp3quCejvdvgraxCsmHTfHouZPcjJSJ09HrQ@mail.gmail.com' \
--to=ps.prateek.sharma143@gmail.com \
--cc=70478@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@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 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).