unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 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 13:13:29 +0300	[thread overview]
Message-ID: <86a5ihir06.fsf@gnu.org> (raw)
In-Reply-To: <87a5iiyrlg.fsf@yahoo.com> (message from Po Lu on Tue, 16 Jul 2024 10:54:03 +0800)

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




  reply	other threads:[~2024-07-16 10:13 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 [this message]
2024-07-16 12:15       ` Philip Kaludercic
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

  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=86a5ihir06.fsf@gnu.org \
    --to=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 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).