From: Ben Boeckel <mathstuf@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Jonathan Corbet <corbet@lwn.net>,
David Howells <dhowells@redhat.com>,
linux-crypto@vger.kernel.org, linux-doc@vger.kernel.org,
keyrings@vger.kernel.org
Subject: Re: [PATCH 02/11] docs: crypto: convert asymmetric-keys.txt to ReST
Date: Thu, 06 Feb 2020 20:09:11 +0000 [thread overview]
Message-ID: <20200206200911.GA2830394@erythro.kitware.com> (raw)
In-Reply-To: <1b6cd1da02dda27a725a6c4214019a1e306a7927.1581001737.git.mchehab+huawei@kernel.org>
On Thu, Feb 06, 2020 at 16:11:21 +0100, Mauro Carvalho Chehab wrote:
> - (1) If the criterion string is of the form "id:<hexdigits>" then the match
> + 1) If the criterion string is of the form "id:<hexdigits>" then the match
This update was followed in all the enumeration changes except…
> - (2) If the criterion string is of the form "<subtype>:<hexdigits>" then the
> + 2) If the criterion string is of the form "<subtype>:<hexdigits>" then the
The whitespace here doesn't match up. Which is preferred?
> - (1) Signature verification.
> +1) Signature verification.
Here, the indentation was lost too. Is this intentional?
--Ben
WARNING: multiple messages have this Message-ID (diff)
From: Ben Boeckel <mathstuf@gmail.com>
To: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>,
Jonathan Corbet <corbet@lwn.net>,
David Howells <dhowells@redhat.com>,
linux-crypto@vger.kernel.org, linux-doc@vger.kernel.org,
keyrings@vger.kernel.org
Subject: Re: [PATCH 02/11] docs: crypto: convert asymmetric-keys.txt to ReST
Date: Thu, 6 Feb 2020 15:09:11 -0500 [thread overview]
Message-ID: <20200206200911.GA2830394@erythro.kitware.com> (raw)
In-Reply-To: <1b6cd1da02dda27a725a6c4214019a1e306a7927.1581001737.git.mchehab+huawei@kernel.org>
On Thu, Feb 06, 2020 at 16:11:21 +0100, Mauro Carvalho Chehab wrote:
> - (1) If the criterion string is of the form "id:<hexdigits>" then the match
> + 1) If the criterion string is of the form "id:<hexdigits>" then the match
This update was followed in all the enumeration changes except…
> - (2) If the criterion string is of the form "<subtype>:<hexdigits>" then the
> + 2) If the criterion string is of the form "<subtype>:<hexdigits>" then the
The whitespace here doesn't match up. Which is preferred?
> - (1) Signature verification.
> +1) Signature verification.
Here, the indentation was lost too. Is this intentional?
--Ben
next prev parent reply other threads:[~2020-02-06 20:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-06 15:11 [PATCH 00/11] Manually convert thermal, crypto and misc-devices to ReST Mauro Carvalho Chehab
2020-02-06 15:11 ` Mauro Carvalho Chehab
2020-02-06 15:11 ` [PATCH 01/11] docs: thermal: convert cpu-idle-cooling.rst " Mauro Carvalho Chehab
2020-02-06 15:11 ` [PATCH 02/11] docs: crypto: convert asymmetric-keys.txt " Mauro Carvalho Chehab
2020-02-06 15:11 ` Mauro Carvalho Chehab
2020-02-06 20:09 ` Ben Boeckel [this message]
2020-02-06 20:09 ` Ben Boeckel
2020-02-10 6:10 ` Mauro Carvalho Chehab
2020-02-10 6:10 ` Mauro Carvalho Chehab
2020-02-06 15:11 ` [PATCH 03/11] docs: crypto: convert api-intro.txt to ReST format Mauro Carvalho Chehab
2020-02-06 15:11 ` [PATCH 04/11] docs: crypto: convert async-tx-api.txt " Mauro Carvalho Chehab
2020-02-06 15:11 ` [PATCH 05/11] docs: crypto: descore-readme.txt: convert " Mauro Carvalho Chehab
2020-02-06 15:11 ` [PATCH 06/11] docs: misc-devices/spear-pcie-gadget.txt: convert to ReST Mauro Carvalho Chehab
2020-02-06 15:11 ` [PATCH 07/11] docs: misc-devices/pci-endpoint-test.txt: " Mauro Carvalho Chehab
2020-02-06 15:11 ` [PATCH 08/11] " Mauro Carvalho Chehab
2020-02-06 15:11 ` [PATCH 09/11] docs: misc-devices/c2port.txt: convert to ReST format Mauro Carvalho Chehab
2020-02-06 15:11 ` [PATCH 10/11] docs: misc-devices/bh1770glc.txt: convert to ReST Mauro Carvalho Chehab
2020-02-06 15:11 ` [PATCH 11/11] docs: misc-devices/apds990x.txt: convert to ReST format Mauro Carvalho Chehab
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=20200206200911.GA2830394@erythro.kitware.com \
--to=mathstuf@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=herbert@gondor.apana.org.au \
--cc=keyrings@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@infradead.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 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.