From: Eli Zaretskii <eliz@gnu.org>
To: rms@gnu.org
Cc: luangruo@yahoo.com, emacs-devel@gnu.org
Subject: Re: master b0049c942b8: bytecomp.el: Warn for `, ' not within backquote construct
Date: Mon, 05 Feb 2024 14:46:42 +0200 [thread overview]
Message-ID: <86ttmn13kd.fsf@gnu.org> (raw)
In-Reply-To: <E1rWpmH-0001yF-0A@fencepost.gnu.org> (message from Richard Stallman on Sun, 04 Feb 2024 22:36:13 -0500)
> From: Richard Stallman <rms@gnu.org>
> Cc: emacs-devel@gnu.org
> Date: Sun, 04 Feb 2024 22:36:13 -0500
>
> > Richard, our ChangeLog generator script is not sophisticated enough to
> > extract file names from the title of a commit. Instead, please move the
> > file name to a separate line, in the format of a ChangeLog entry:
>
> > * lisp/emacs-lisp/bytecomp.el:
>
> 1. The format I used on Feb 3 was the same as used in the previous
> commit for that same file. What exactly are you asking me to do
> differently?
To name the file name before the function name:
* lisp/emacs-lisp/bytecomp.el (bytecomp--report-comma): New function with...
You could still mention the file name in the heading line (the 1st
line of the log message), it does no harm to have the file mentioned
twice.
> 2. How could I change it now that it is already pushed?
You cannot. We can only edit by hand the produced ChangeLog when the
next release's tarball is being prepared.
next prev parent reply other threads:[~2024-02-05 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170700201601.3724.18410252880023545872@vcs2.savannah.gnu.org>
[not found] ` <20240203231336.5A511C0EFF8@vcs2.savannah.gnu.org>
2024-02-04 4:06 ` master b0049c942b8: bytecomp.el: Warn for `, ' not within backquote construct Po Lu
2024-02-05 3:36 ` Richard Stallman
2024-02-05 12:46 ` Eli Zaretskii [this message]
2024-02-05 13:35 ` Stefan Monnier via Emacs development discussions.
2024-03-16 1:45 ` Richard Stallman
2024-03-16 15:08 ` Stefan Monnier
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=86ttmn13kd.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=rms@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).