From: Yuan Fu <casouri@gmail.com>
To: Visuwesh <visuweshm@gmail.com>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: feature/tree-sitter 34e50dc4a2 2/5: Allow tree-sitter to notify parse-tree changes
Date: Tue, 15 Nov 2022 10:20:24 -0800 [thread overview]
Message-ID: <9D54C3C3-0821-4A05-838B-416A49018008@gmail.com> (raw)
In-Reply-To: <874jv0w0r5.fsf@gmail.com>
>> From: Yuan Fu <casouri@gmail.com>
>> Date: Tue, 15 Nov 2022 09:25:27 -0800
>> Cc: emacs-devel@gnu.org
>>
>> BTW how do you send an email like this, with the tile being the commit message and everything?
>
> See https://lists.gnu.org/archive/html/emacs-diffs/2022-11/index.html.
> On Nov 15, 2022, at 10:06 AM, Visuwesh <visuweshm@gmail.com> wrote:
>
> [செவ்வாய் நவம்பர் 15, 2022] Yuan Fu wrote:
>
>> BTW how do you send an email like this, with the tile being the commit message and everything?
>
> I believe Po Lu follows emacs-diffs. All emacs-diffs messages have the
> subject as the commit summary and the entire commit in the body, and
> they have the mail headers set up so that the messaege is sent to the
> commit author whilst having emacs-devel in the CC's.
>
>> Yuan
Ahhh, how nice. Thanks to you both! Subscribing to yet one more emacs ML ;-)
Yuan
prev parent reply other threads:[~2022-11-15 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166850936462.27011.17289179422833914249@vcs2.savannah.gnu.org>
[not found] ` <20221115104926.4D491C0E4C8@vcs2.savannah.gnu.org>
2022-11-15 11:52 ` feature/tree-sitter 06db8015ea 1/5: Extract out treesit_make_ranges Po Lu
[not found] ` <20221115104926.5143AC0E4CA@vcs2.savannah.gnu.org>
2022-11-15 11:54 ` feature/tree-sitter 34e50dc4a2 2/5: Allow tree-sitter to notify parse-tree changes Po Lu
2022-11-15 17:25 ` Yuan Fu
2022-11-15 18:06 ` Eli Zaretskii
2022-11-15 18:06 ` Visuwesh
2022-11-15 18:20 ` Yuan Fu [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=9D54C3C3-0821-4A05-838B-416A49018008@gmail.com \
--to=casouri@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=visuweshm@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).