linux-kernel - Re: [PATCH] docs: sphinx: Trivial fix of a typo in the file rstFlatTable.py

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <877dlv15hu.fsf@meer.lwn.net>
Date:   Thu, 25 Mar 2021 11:57:01 -0600
From:   Jonathan Corbet <corbet@....net>
To:     Bhaskar Chowdhury <unixbhaskar@...il.com>, unixbhaskar@...il.com,
        linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:     rdunlap@...radead.org
Subject: Re: [PATCH] docs: sphinx:  Trivial fix of a typo in the file
 rstFlatTable.py

Bhaskar Chowdhury <unixbhaskar@...il.com> writes:

> s/buidler/builder/
>
> Signed-off-by: Bhaskar Chowdhury <unixbhaskar@...il.com>
> ---
>  Documentation/sphinx/rstFlatTable.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/sphinx/rstFlatTable.py b/Documentation/sphinx/rstFlatTable.py
> index a3eea0bbe6ba..1d2b9be6b6c5 100755
> --- a/Documentation/sphinx/rstFlatTable.py
> +++ b/Documentation/sphinx/rstFlatTable.py
> @@ -161,7 +161,7 @@ class ListTableBuilder(object):
>          for colwidth in colwidths:
>              colspec = nodes.colspec(colwidth=colwidth)
>              # FIXME: It seems, that the stub method only works well in the
> -            # absence of rowspan (observed by the html buidler, the docutils-xml
> +            # absence of rowspan (observed by the html builder, the docutils-xml
>              # build seems OK).  This is not extraordinary, because there exists
>              # no table directive (except *this* flat-table) which allows to
>              # define coexistent of rowspan and stubs (there was no use-case
> --

This was fixed in your previous patch from March 2.  Bhaskar, please
slow down a bit and try not to create needless work for the recipients
of your patches, OK?

Thanks,

jon