From: Noah Peart <noah.v.peart@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: casouri@gmail.com, 70465@debbugs.gnu.org
Subject: bug#70465: [PATCH] Add font-locking rule for Rust function signatures
Date: Fri, 19 Apr 2024 10:43:48 -0700 [thread overview]
Message-ID: <CAPVBTSe95PPb9UV7NU7OmfdFT=_Vt+9ZMXk6H1NfdGMK+VCE0g@mail.gmail.com> (raw)
In-Reply-To: <86wmot9rxk.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
Got it, thanks!
On Fri, Apr 19, 2024 at 10:35 AM Eli Zaretskii <eliz@gnu.org> wrote:
> > From: Noah Peart <noah.v.peart@gmail.com>
> > Date: Fri, 19 Apr 2024 09:47:38 -0700
> > Cc: Yuan Fu <casouri@gmail.com>, 70465@debbugs.gnu.org
> >
> > > Please be sure to add the bug number to the commit log message when
> > you install this.
> >
> > When submitting a patch, is there an easy way to add the bug number to
> > the commit?
>
> Only after you get the bug report back from the bug tracker. When you
> send the first message which creates a new bug report, you cannot know
> it. So we only ask people to add the bug number if they submit a
> revised patch, because at that point the number is already known.
> When an original patch is installed, the person who pushes it must do
> a "git commit --amend" to edit the commit log message to add the bug
> number.
>
[-- Attachment #2: Type: text/html, Size: 1423 bytes --]
next prev parent reply other threads:[~2024-04-19 17:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 2:01 bug#70465: [PATCH] Add font-locking rule for Rust function signatures Noah Peart
2024-04-19 7:24 ` Yuan Fu
2024-04-19 10:47 ` Eli Zaretskii
2024-04-19 16:47 ` Noah Peart
2024-04-19 17:35 ` Eli Zaretskii
2024-04-19 17:43 ` Noah Peart [this message]
2024-04-22 0:03 ` 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='CAPVBTSe95PPb9UV7NU7OmfdFT=_Vt+9ZMXk6H1NfdGMK+VCE0g@mail.gmail.com' \
--to=noah.v.peart@gmail.com \
--cc=70465@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).