From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: master b0049c942b8: bytecomp.el: Warn for `, ' not within backquote construct Date: Mon, 05 Feb 2024 14:46:42 +0200 Message-ID: <86ttmn13kd.fsf@gnu.org> References: <170700201601.3724.18410252880023545872@vcs2.savannah.gnu.org> <20240203231336.5A511C0EFF8@vcs2.savannah.gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11845"; mail-complaints-to="usenet@ciao.gmane.io" Cc: luangruo@yahoo.com, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Feb 05 13:48:02 2024 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rWyOI-0002rU-Nm for ged-emacs-devel@m.gmane-mx.org; Mon, 05 Feb 2024 13:48:02 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rWyNe-0003Zz-P9; Mon, 05 Feb 2024 07:47:24 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rWyNK-0003WA-5I for emacs-devel@gnu.org; Mon, 05 Feb 2024 07:47:02 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rWyNJ-0008PE-OQ; Mon, 05 Feb 2024 07:47:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=7dUUE25+O6Qb/5ff4LrFeTOCcGP+v3wF8HiJlqX/lzU=; b=IXLkjvyAHGyJ IuTXfONfmUR5YRLozxXnOonwhowp+9PEhWHVfQ95ckWvc0oiGwPDCNBxvwzK/eijX65l6c59DhAiw qW4je7KUGCIecZ/so8zVR9OC4twOLhWJuoQOX52i+8tiRfZb7Ur2Yggm7e9YKVFfJs2sW0tcuxY9w wLtckTkFJ/9h5dRcXmcWYyec7Z3KembtwRmY8e3E+r7L2z/UTQA1tpLi524mclfeSlihFUfYC3MFq ah+RlnqyTp7kai3I40uX0dCt2JDu3bCosnLCDVw3SbncdE0nwW2BC4fCsoMinebnCCKI1WOtnfRgC 2nMab29b3LLT5W7rPpY71Q==; In-Reply-To: (message from Richard Stallman on Sun, 04 Feb 2024 22:36:13 -0500) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:315887 Archived-At: > From: Richard Stallman > 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.