lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 8 Aug 2018 15:45:27 +0200
From:   Daniel Borkmann <>
To:     Jonathan Corbet <>, "Tobin C. Harding" <>
Cc:     Alexei Starovoitov <>,
        "David S. Miller" <>,,,
Subject: Re: [PATCH bpf-next 12/13] docs: net: Fix various minor typos

On 08/08/2018 03:23 PM, Jonathan Corbet wrote:
> On Wed, 8 Aug 2018 11:42:48 +1000
> "Tobin C. Harding" <> wrote:
>> Thanks for doing such a careful review that you noticed this.  I'm
>> working on this more ATM and I've moved the document to use double
>> spaces between _all_ full stops.  Currently the document uses mostly
>> single spaces but there are some sections with double space.  The
>> internet tells me this is a 'style' issue not a rule.  And I've seen
>> single and double spacing in tree and do not know if one is favoured.
>> Do you care? 
> I'm not Daniel, but let me just say that, for docs in general, I'm
> absolutely uninterested in patches adjusting the number of spaces after
> periods.  It really doesn't matter one way or the other, and I don't think
> we benefit from that kind of churn.

Yep, agree.

Powered by blists - more mailing lists