From: Eli Zaretskii <eliz@gnu.org>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: rahguzar@zohomail.eu, 69555-done@debbugs.gnu.org
Subject: bug#69555: 30.0.50; shr - Preserve indentation when shr-fill-text is nil
Date: Fri, 15 Mar 2024 10:48:53 +0200 [thread overview]
Message-ID: <86sf0r98y2.fsf@gnu.org> (raw)
In-Reply-To: <87y1akj7hq.fsf@gmail.com> (message from Kévin Le Gouguec on Fri, 15 Mar 2024 08:10:09 +0100)
> From: Kévin Le Gouguec <kevin.legouguec@gmail.com>
> Cc: rahguzar@zohomail.eu, 69555-done@debbugs.gnu.org
> Date: Fri, 15 Mar 2024 08:10:09 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > . use only ASCII characters in the commit log message
>
> (ACK; FWIW I did check the repo log for a precedent when adding those
> ellipses. Wondering if build-aux/git-hooks/commit-msg ought to report
> this? It does seem to explicitly check for non-UTF-8)
I'm against making our commit hooks more strict, as they are already
quite a nuisance in some situations, for example, when merging from
the release branch. It isn't a catastrophe when UTF-8 encoded
non-ASCII characters snick into our logs, so it's a soft preference,
not something we should enforce by rejecting commits.
prev parent reply other threads:[~2024-03-15 8:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 22:02 bug#69555: 30.0.50; shr - Preserve indentation when shr-fill-text is nil Kévin Le Gouguec
2024-03-04 22:08 ` Kévin Le Gouguec
2024-03-05 12:09 ` Eli Zaretskii
2024-03-05 19:22 ` Kévin Le Gouguec
2024-03-05 19:47 ` Eli Zaretskii
2024-03-05 23:16 ` Kévin Le Gouguec
2024-03-06 11:53 ` Eli Zaretskii
2024-03-06 21:18 ` Kévin Le Gouguec
2024-03-07 6:39 ` Eli Zaretskii
2024-03-06 7:27 ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-13 19:55 ` Kévin Le Gouguec
2024-03-13 20:28 ` Rahguzar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-13 21:41 ` Kévin Le Gouguec
2024-03-14 5:04 ` Eli Zaretskii
2024-03-15 7:10 ` Kévin Le Gouguec
2024-03-15 8:48 ` Eli Zaretskii [this message]
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=86sf0r98y2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69555-done@debbugs.gnu.org \
--cc=kevin.legouguec@gmail.com \
--cc=rahguzar@zohomail.eu \
/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).