public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH v2] memcmp.3: Recast security caveat
Date: Mon, 31 Jul 2023 13:53:50 +0200	[thread overview]
Message-ID: <1ba61d3b-d5b8-c7ef-9535-b349b501710c@kernel.org> (raw)
In-Reply-To: <20230731110630.e6zmzvskibdbvp6b@illithid>


[-- Attachment #1.1: Type: text/plain, Size: 2409 bytes --]

Hi Branden,

On 2023-07-31 13:06, G. Branden Robinson wrote:
> Hi Alex,
> 
> At 2023-07-30T19:31:39+0200, Alejandro Colomar wrote:
>> On 2023-07-30 17:31, G. Branden Robinson wrote:
>>> Use terminology more carefully.
>>>
>>> * Refer to the info sec property of confidentiality instead of saying,
>>>   vaguely, "security-critical".
>>>     https://informationsecurity.wustl.edu/items/\
>>>     confidentiality-integrity-and-availability-the-cia-triad/
>>> * Try not to confuse anyone who's studied the analysis of algorithms:
>>>   don't say "constant time" when "deterministic time" is meant.  The
>>>   time to perform the memory comparison remains linear (O(n)), not
>>>   constant (O(1)).
>>> * Tighten wording.
>>
>> I prefer 2 spaces between the bullet and the list contents.  See
>> man-pages(7).  Anyway, I accepted it this time.  :)
> 
> This had me confused for a while, since I had no tagged paragraphs in
> the patch.  You must mean in the commit message, too.

Yup; sorry; I did mean the commit message, yes.

>  I don't think
> that's documented...?  I guess it should go in the "CONTRIBUTING" file.

I didn't document it in CONTRIBUTING, because usually I don't receive
bulleted lists in commit messages.  Only you and Paul Eggert seem to
send of those (no problem with that, though; they are fine).

The only documentation is in man-pages(7), since man(7) source is the
only place where they are commonly used in the project:

   Lists
       There are different kinds of lists:

       [...]

       Bullet lists
              Elements are preceded by bullet symbols  (\[bu]).   Any‐
              thing  that  doesn’t fit elsewhere is usually covered by
              this type of list.

       [...]

       There should always be exactly 2 spaces between the list symbol
       and the elements.  This doesn’t apply to  "tagged  paragraphs",
       which use the default indentation rules.


> 
>> You need to quote your name with '"' due to the '.'.  I've found
>> some software has issues with it.  git-send-email(1) is one of them
>> (due to the perl library it uses).
> 
> Thanks--I fixed my vi ":ab" command to take care of this.

Nice; I didn't know of :ab :)

Cheers,
Alex

> 
> Regards,
> Branden

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-07-31 11:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-30 15:31 [PATCH v2] memcmp.3: Recast security caveat G. Branden Robinson
2023-07-30 17:31 ` Alejandro Colomar
2023-07-31 11:06   ` G. Branden Robinson
2023-07-31 11:53     ` Alejandro Colomar [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=1ba61d3b-d5b8-c7ef-9535-b349b501710c@kernel.org \
    --to=alx@kernel.org \
    --cc=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.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