unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: master 511bd2b8bc3: Make emerge-m-t-f obsolete in favor of make-temp-file
Date: Sat, 2 Sep 2023 15:57:49 +0200	[thread overview]
Message-ID: <CADwFkm=ddpz-ej8BrDxZ-nhX2Cip0Aj8T3sanh1JfJMBBu6ZrA@mail.gmail.com> (raw)
In-Reply-To: <87h6ocn2wl.fsf@yahoo.com>

Po Lu <luangruo@yahoo.com> writes:

> > branch: master
> > commit 511bd2b8bc32b2867bd8d63311d827a821e6ef47
> > Author: Stefan Kangas <stefankangas@gmail.com>
> > Commit: Stefan Kangas <stefankangas@gmail.com>
> >
> >     Make emerge-m-t-f obsolete in favor of make-temp-file
> >
> >     * lisp/vc/emerge.el (emerge-make-temp-file): Make obsolete in favor of
> >     'make-temp-file'.  Update all callers.
>
> Btw, folks, this is an exemplar of the kind of commit that doesn't
> warrant a commit title: the log entry itself is perfectly adequate.

That advice is fine for one line entries.  If the log entry is two
lines, it will be hard to read in displays that only show the first
line.

> 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?



  reply	other threads:[~2023-09-02 13:57 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 [this message]
2023-09-02 14:11       ` Po Lu
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='CADwFkm=ddpz-ej8BrDxZ-nhX2Cip0Aj8T3sanh1JfJMBBu6ZrA@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.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).