From: Sean Whitton <spwhitton@spwhitton.name>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: ChangeLog and commit messages
Date: Sun, 18 Jun 2023 08:44:19 +0100 [thread overview]
Message-ID: <87a5wx1agc.fsf@melete.silentflame.com> (raw)
In-Reply-To: <87a5wxb5sl.fsf@yahoo.com> (Po Lu's message of "Sun, 18 Jun 2023 15:14:50 +0800")
Hello,
On Sun 18 Jun 2023 at 03:14PM +08, Po Lu wrote:
> I find myself often frustrated that Git requires a commit title. In
> such a title, committers are expected to summarize in detail changes to
> dozens of different functions in less than 74 characters of text.
Yes, it doesn't fit well with Emacs changelog practices ...
> Normally, the place for such descriptions would be in ChangeLog and
> not the commit message title. Would it be possible to allow writing
> commit messages consisting solely of ChangeLog, forgoing the commit
> title entirely?
... but this renders C-x v L so much less useful, and anyone who uses
git for other projects will be used to using that view of things a lot.
--
Sean Whitton
next prev parent reply other threads:[~2023-06-18 7:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87a5wxb5sl.fsf.ref@yahoo.com>
2023-06-18 7:14 ` ChangeLog and commit messages Po Lu
2023-06-18 7:39 ` Eli Zaretskii
2023-06-18 7:41 ` Po Lu
2023-06-18 8:02 ` Eli Zaretskii
2023-06-18 14:50 ` Konstantin Kharlamov
2023-06-19 0:48 ` Po Lu
2023-06-19 6:25 ` Konstantin Kharlamov
2023-06-19 6:51 ` Po Lu
2023-06-19 9:07 ` Konstantin Kharlamov
2023-06-19 10:10 ` Po Lu
2023-06-19 11:57 ` Dmitry Gutov
2023-06-19 16:59 ` Eli Zaretskii
2023-06-19 17:24 ` Dmitry Gutov
2023-06-19 22:18 ` Konstantin Kharlamov
2023-06-19 16:33 ` Eli Zaretskii
2023-06-20 0:55 ` Po Lu
2023-06-23 6:50 ` Sean Whitton
2023-06-23 7:16 ` Eli Zaretskii
2023-06-18 7:44 ` Sean Whitton [this message]
2023-06-18 22:38 ` Dmitry Gutov
2023-06-19 8:52 ` Jose E. Marchesi
2023-06-18 14:03 Bruno Haible
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=87a5wx1agc.fsf@melete.silentflame.com \
--to=spwhitton@spwhitton.name \
--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).