From: Po Lu <luangruo@yahoo.com>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: master 9ccaa09a635: ; .dir-locals.el (log-edit-mode) <fill-column>: Set to 64.
Date: Thu, 08 Feb 2024 09:36:13 +0800 [thread overview]
Message-ID: <87plx74u0i.fsf@yahoo.com> (raw)
In-Reply-To: <CADwFkmmK+r6Q_GdTa++PaZRm3ngQ_ueXR2yfzN8RaS607dUiOg@mail.gmail.com> (Stefan Kangas's message of "Wed, 7 Feb 2024 12:01:14 -0800")
Stefan Kangas <stefankangas@gmail.com> writes:
> This change breaks with our conventions and historical practice, and
> makes both commit messages and ChangeLogs take up much more vertical
> space for no practical benefit.
??? Our historical and current practice is to fill ChangeLogs to 74
columns, which setting the fill-column in log messages to 64
accomplishes. See CONTRIBUTE:
- Lines in ChangeLog entries should preferably be not longer than 63
characters, and must not exceed 78 characters, unless they consist
of a single word of at most 140 characters; this 78/140 limit is
enforced by a commit hook.
or any of the old hand-written ChangeLog files.
next prev parent reply other threads:[~2024-02-08 1:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170727415485.32408.11264518274307262467@vcs2.savannah.gnu.org>
[not found] ` <20240207024915.38686C0EFEC@vcs2.savannah.gnu.org>
2024-02-07 20:01 ` master 9ccaa09a635: ; .dir-locals.el (log-edit-mode) <fill-column>: Set to 64 Stefan Kangas
2024-02-08 1:36 ` Po Lu [this message]
2024-02-08 3:10 ` Jim Porter
2024-02-08 3:34 ` Po Lu
2024-02-08 6:13 ` Jim Porter
2024-02-08 7:23 ` Eli Zaretskii
2024-02-08 17:49 ` Jim Porter
2024-02-08 19:30 ` Eli Zaretskii
2024-02-08 20:21 ` Jim Porter
2024-02-08 20:30 ` Eli Zaretskii
2024-02-18 2:00 ` Stefan Kangas
2024-02-18 3:16 ` Po Lu
2024-02-18 11:36 ` bug#69223: 30.0.50; fill-column in log-edit-mode wraps ChangeLog entries incorrectly Stefan Kangas
2024-02-08 7:09 ` master 9ccaa09a635: ; .dir-locals.el (log-edit-mode) <fill-column>: Set to 64 Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87plx74u0i.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.