lists.openwall.net | 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 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <355309ce-3b3b-9d1b-6b4e-5e867bba920a@gmail.com> Date: Tue, 28 Mar 2023 15:38:44 +0700 From: Bagas Sanjaya <bagasdotme@...il.com> To: Akira Yokosawa <akiyks@...il.com> Cc: corbet@....net, davem@...emloft.net, donald.hunter@...il.com, donald.hunter@...hat.com, edumazet@...gle.com, kuba@...nel.org, linux-doc@...r.kernel.org, netdev@...r.kernel.org, pabeni@...hat.com Subject: Re: [PATCH net-next v5 6/7] docs: netlink: document struct support for genetlink-legacy On 3/27/23 21:39, Akira Yokosawa wrote: >> Nit: The indentation for code-block codes should be relative to >> code-block:: declaration (e.g. if it starts from column 4, the first >> column of code is also at 4). > > Hey Bagas, > > I don't believe there is any such restriction. :-\ > Where did you find it ? > This current doc renders well (no warnings), but personally I found that aligning codes in the code-block:: is aesthetically better in my eyes (I expect the leading spaces as margin). -- An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists