public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zackw@panix.com>
To: Rafal Luzynski <digitalfreak@lingonborough.com>
Cc: GNU C Library <libc-alpha@sourceware.org>, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH 03/12] Don’t use the argument to time.
Date: Tue, 20 Aug 2019 17:21:00 -0000	[thread overview]
Message-ID: <CAKCAbMjdQHng9QOHaNbqVd_fOKZsQZ42=mxSGac3vb69FERAcQ@mail.gmail.com> (raw)
In-Reply-To: <470439858.757909.1566320907353@poczta.nazwa.pl>

On Tue, Aug 20, 2019 at 1:09 PM Rafal Luzynski
<digitalfreak@lingonborough.com> wrote:
> Zack, I think that your email software replaces the plain ASCII
> apostrophe character "'" (ASCII/Unicode 0x0027) with the right single
> quotation mark character "’" (Unicode 0x2019).  I am not sure if
> we want this in the git comments if possible to keep the plain
> ASCII.  This applies to other patches as well.

That was actually my text editor when I wrote the commit messages in
the first place, but it's a fair question anyway.  What _is_ our
policy on non-ASCII characters in general, and "smart" / "typographic"
quote marks in particular, in commit messages and ChangeLogs?

zw

  reply	other threads:[~2019-08-20 17:21 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-20 13:22 [PATCH 00/12] Y2038 preparation: use clock_[gs]ettime to implement the other time-getting and -setting functions Zack Weinberg
2019-08-20 13:21 ` [PATCH 03/12] Don’t use the argument to time Zack Weinberg
2019-08-20 17:09   ` Rafal Luzynski
2019-08-20 17:21     ` Zack Weinberg [this message]
2019-08-20 17:36     ` Joseph Myers
2019-08-22  9:42       ` Rafal Luzynski
2019-08-22  9:49         ` Florian Weimer
2019-08-23 20:26           ` Spelling of contributor names (was: [PATCH 03/12] Don’t use the argument to time) Paul Eggert
2019-08-23 20:49             ` Joseph Myers
2019-08-23 20:51               ` Joseph Myers
2019-08-23 21:28                 ` Paul Eggert
2019-08-24  5:58                   ` Spelling of contributor names Florian Weimer
2019-08-25  0:56                     ` Paul Eggert
2019-08-27 15:58                       ` Joseph Myers
2019-08-23 22:07             ` Spelling of contributor names (was: [PATCH 03/12] Don’t use the argument to time) Rafal Luzynski
2019-08-23 22:31               ` Paul Eggert
2019-08-26 14:42             ` Spelling of contributor names Stefan Liebler
2019-08-20 18:08   ` [PATCH 03/12] Don’t use the argument to time Adhemerval Zanella
2019-08-21 12:29     ` Zack Weinberg
2019-08-22  9:37       ` Rafal Luzynski
2019-08-20 13:22 ` [PATCH 05/12] Use clock_settime to implement settimeofday Zack Weinberg
2019-08-20 13:22 ` [PATCH 09/12] Finish move of clock_* functions to libc Zack Weinberg
2019-08-20 15:13   ` Joseph Myers
2019-08-20 15:19     ` Zack Weinberg
2019-08-20 15:21     ` Florian Weimer
2019-08-20 15:25       ` Zack Weinberg
2019-08-20 13:22 ` [PATCH 01/12] Remove implementations of clock_[gs]ettime using [gs]ettimeofday Zack Weinberg
2019-08-20 18:06   ` Adhemerval Zanella
2019-08-22 12:54     ` Zack Weinberg
2019-08-23 17:49       ` Adhemerval Zanella
2019-08-20 13:22 ` [PATCH 12/12] Revise the documentation of ‘simple calendar time’ Zack Weinberg
2019-08-20 18:50   ` Paul Eggert
2019-08-20 19:38     ` Joseph Myers
2019-08-20 19:55       ` Zack Weinberg
2019-08-20 20:19     ` Zack Weinberg
2019-08-20 20:23       ` Zack Weinberg
2019-08-20 13:22 ` [PATCH 04/12] Use clock_settime to implement stime Zack Weinberg
2019-08-21 15:10   ` Adhemerval Zanella
2019-08-22 12:57     ` Zack Weinberg
2019-08-20 13:22 ` [PATCH 02/12] Change most internal uses of __gettimeofday to __clock_gettime Zack Weinberg
2019-08-20 18:53   ` Paul Eggert
2019-08-22 12:55     ` Zack Weinberg
2019-08-20 20:56   ` Adhemerval Zanella
2019-08-21 21:09     ` Zack Weinberg
2019-08-23 18:39       ` Adhemerval Zanella
2019-08-20 13:37 ` [PATCH 11/12] Linux/Alpha: don’t use timeval32 system calls Zack Weinberg
2019-08-21 18:50   ` Adhemerval Zanella
2019-08-22 13:36     ` Zack Weinberg
2019-08-23 18:48       ` Adhemerval Zanella
2019-08-20 13:37 ` [PATCH 08/12] Use clock_gettime to implement gettimeofday Zack Weinberg
2019-08-20 15:24   ` Joseph Myers
2019-08-22 13:01     ` Zack Weinberg
2019-08-27 14:34       ` Arnd Bergmann
2019-08-20 17:51   ` Adhemerval Zanella
2019-08-20 13:37 ` [PATCH 07/12] Use clock_gettime to implement ftime Zack Weinberg
2019-08-21 15:18   ` Adhemerval Zanella
2019-08-22 12:59     ` Zack Weinberg
2019-08-20 13:37 ` [PATCH 06/12] Use clock_gettime to implement time Zack Weinberg
2019-08-20 18:02   ` Adhemerval Zanella
2019-08-22 12:58     ` Zack Weinberg
2019-08-20 13:56 ` [PATCH 10/12] Warn when gettimeofday is called with non-null tzp argument Zack Weinberg
2019-08-20 18:52   ` Paul Eggert
2019-08-20 19:03     ` Zack Weinberg
2019-08-20 19:06       ` Paul Eggert
2019-08-21 15:30   ` Adhemerval Zanella
2019-08-21 16:03     ` Zack Weinberg
2019-08-21 16:10       ` Florian Weimer
2019-08-22 13:07         ` Zack Weinberg
2019-08-23 13:05           ` Florian Weimer
2019-08-20 15:10 ` [PATCH 00/12] Y2038 preparation: use clock_[gs]ettime to implement the other time-getting and -setting functions Joseph Myers
2019-08-20 15:21   ` Zack Weinberg
2019-08-20 18:47 ` Alistair Francis
2019-08-20 18:55 ` Paul Eggert
2019-08-21  8:00 ` Lukasz Majewski

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='CAKCAbMjdQHng9QOHaNbqVd_fOKZsQZ42=mxSGac3vb69FERAcQ@mail.gmail.com' \
    --to=zackw@panix.com \
    --cc=arnd@arndb.de \
    --cc=digitalfreak@lingonborough.com \
    --cc=libc-alpha@sourceware.org \
    /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.
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).