linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Micah Morton <mortonm@chromium.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Christian Kujau <lists@nerdbynature.de>,
	linux-doc@vger.kernel.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [TYPO] SafeSetID.rst: Remove spurious '???' characters
Date: Fri, 11 Oct 2019 09:23:40 -0700	[thread overview]
Message-ID: <CAJ-EccOz+DeC=y1ToBhq2F-sos0g+_6iWK8vjXgxuENGsn7Few@mail.gmail.com> (raw)
In-Reply-To: <20191011100018.0e9fff37@lwn.net>

Ah, thanks for this. We had this fixed in
http://kernsec.org/pipermail/linux-security-module-archive/2019-May/013525.html,
but looks like it got forgotten somehow.

On Fri, Oct 11, 2019 at 9:00 AM Jonathan Corbet <corbet@lwn.net> wrote:
>
> On Thu, 10 Oct 2019 20:36:16 -0700 (PDT)
> Christian Kujau <lists@nerdbynature.de> wrote:
>
> > While reading SafeSetID.rst I stumbled across those things. This patch
> > removes these spurious '???' characters.
> >
> > Signed-off-by: Christian Kujau <lists@nerdbynature.de>
>
> I've applied this, thanks.  I did take the liberty of rewriting the
> changelog to adhere to normal standards:
>
> Author: Christian Kujau <lists@nerdbynature.de>
> Date:   Thu Oct 10 20:36:16 2019 -0700
>
>     docs: SafeSetID.rst: Remove spurious '???' characters
>
>     It appears that some smart quotes were changed to "???" by even smarter
>     software; change them to the dumb but legible variety.
>
>     Signed-off-by: Christian Kujau <lists@nerdbynature.de>
>     Signed-off-by: Jonathan Corbet <corbet@lwn.net>
>
> Thanks,
>
> jon

      reply	other threads:[~2019-10-11 16:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11  3:36 [TYPO] SafeSetID.rst: Remove spurious '???' characters Christian Kujau
2019-10-11 16:00 ` Jonathan Corbet
2019-10-11 16:23   ` Micah Morton [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJ-EccOz+DeC=y1ToBhq2F-sos0g+_6iWK8vjXgxuENGsn7Few@mail.gmail.com' \
    --to=mortonm@chromium.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lists@nerdbynature.de \
    /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 NNTP newsgroup(s).