From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Prateek Sharma <ps.prateek.sharma143@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: Sun, 21 Apr 2024 16:39:40 -0700 [thread overview]
Message-ID: <BD3D25F0-9677-471A-920C-9F5C1C44D9CF@gmail.com> (raw)
In-Reply-To: <86a5ln8ev5.fsf@gnu.org>
> On Apr 20, 2024, at 10:27 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Yuan Fu <casouri@gmail.com>
>> Date: Sat, 20 Apr 2024 20:47:29 -0700
>> Cc: Eli Zaretskii <eliz@gnu.org>,
>> 70478@debbugs.gnu.org
>>
>>> On Sat, Apr 20, 2024 at 1:11 PM Eli Zaretskii <eliz@gnu.org> wrote:
>>>> From: Prateek Sharma <ps.prateek.sharma143@gmail.com>
>>>> Date: Sat, 20 Apr 2024 12:25:24 +0530
>>>> Cc: Yuan Fu <casouri@gmail.com>, 70478@debbugs.gnu.org
>>>>
>>>> Also should I squash the changes of both the above commits into one and then create a patch file?
>>>
>>> You should squash, yes. Other than that, attaching the patches as you
>>> did is fine.
>>>
>>> Thanks.
>>> <0001-Fix-treesitter-font-lock-settings-for-built-in-funct.patch>
>>
>> Thanks! Should I apply this to master or emacs-29? It’s a fix so I think emacs-29?
>
> Yes, emacs-29 is fine.
Merged. BTW, Prateek, make sure to wrap the title and body of the commit message, and not end the title with a period. 😊
Yuan
next prev parent reply other threads:[~2024-04-21 23:39 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 [this message]
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
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=BD3D25F0-9677-471A-920C-9F5C1C44D9CF@gmail.com \
--to=casouri@gmail.com \
--cc=70478@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ps.prateek.sharma143@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).