From: Po Lu <luangruo@yahoo.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: master 511bd2b8bc3: Make emerge-m-t-f obsolete in favor of make-temp-file
Date: Sat, 02 Sep 2023 22:11:26 +0800 [thread overview]
Message-ID: <s0d5y4sbr75.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkm=ddpz-ej8BrDxZ-nhX2Cip0Aj8T3sanh1JfJMBBu6ZrA@mail.gmail.com> (Stefan Kangas's message of "Sat, 2 Sep 2023 15:57:49 +0200")
Stefan Kangas <stefankangas@gmail.com> writes:
>> Since Git doesn't provide for empty commit titles, is there some
>> convention we can adopt to guarantee that the redundant title isn't
>> reproduced within generated ChangeLog files? If you compare
>> ChangeLog.android now to its contents when it was first checked in,
>> you'll quickly understand my point.
>
> I don't understand what you're asking, sorry. What is the problem you
> see in ChangeLog.android?
It's not what I see now, but rather what I saw. On 4 August, it was
replete with badly formatted entries, but more pointedly entries with
completely redundant and meaningless commit titles, which I was forced
to manually remove.
next prev parent reply other threads:[~2023-09-02 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <169365938167.11958.8129920473793295512@vcs2.savannah.gnu.org>
[not found] ` <20230902125621.EE120C045B4@vcs2.savannah.gnu.org>
2023-09-02 13:03 ` master 511bd2b8bc3: Make emerge-m-t-f obsolete in favor of make-temp-file Po Lu
2023-09-02 13:57 ` Stefan Kangas
2023-09-02 14:11 ` Po Lu [this message]
2023-09-02 14:21 ` Stefan Kangas
2023-09-02 14:54 ` Po Lu
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=s0d5y4sbr75.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=emacs-devel@gnu.org \
--cc=stefankangas@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).