From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Po Lu <luangruo@yahoo.com>,
emacs-devel@gnu.org, stefankangas@gmail.com
Subject: Re: master fcb4d89aaa7 2/3: Prefer `memcpy` to `strcpy` in image.c
Date: Tue, 16 Jul 2024 12:15:02 +0000 [thread overview]
Message-ID: <87cyndsfcp.fsf@posteo.net> (raw)
In-Reply-To: <86a5ihir06.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 16 Jul 2024 13:13:29 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Po Lu <luangruo@yahoo.com>
>> Cc: Stefan Kangas <stefankangas@gmail.com>
>> Date: Tue, 16 Jul 2024 10:54:03 +0800
>>
>> Stefan Kangas <stefankangas@gmail.com> writes:
>>
>> > branch: master
>> > commit fcb4d89aaa7bf3ed77aaa4d6d5047a0ec2ed9225
>> > Author: Stefan Kangas <stefankangas@gmail.com>
>> > Commit: Stefan Kangas <stefankangas@gmail.com>
>> >
>> > Prefer `memcpy` to `strcpy` in image.c
>>
>> Could we agree not to insert pairs of "``" as quotation marks in commit
>> messages, source code comments, and the like? It gives me the
>> impression of reading a poorly typeset document whose authors were
>> either ignorant of or unwilling to correct directional quotation marks
>> inserted by their input methods.
>
> Our conventions are to quote 'like this' or `like this' in commit log
> messages. Please, everybody, don't use the Markdown-style `like this`
> quoting.
My understanding was that commit logs were to only include 'this this',
while `like this' was only to be used in Elisp docstring and comments?
--
Philip Kaludercic on peregrine
next prev parent reply other threads:[~2024-07-16 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <172109597956.10135.3773889760488581016@vcs2.savannah.gnu.org>
[not found] ` <20240716021300.67222C3534C@vcs2.savannah.gnu.org>
2024-07-16 2:54 ` master fcb4d89aaa7 2/3: Prefer `memcpy` to `strcpy` in image.c Po Lu
2024-07-16 10:13 ` Eli Zaretskii
2024-07-16 12:15 ` Philip Kaludercic [this message]
2024-07-16 12:21 ` Robert Pluim
2024-07-16 13:34 ` 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=87cyndsfcp.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--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.