Re: [PATCH] Documentation: fuse: harmonize numeration

[Randy Dunlap]

On 9/2/26 7:35 AM, Manuel Ebner wrote:
> Replace with '1.', '2.' with '1)', '2)' to harmonize file.
> 

Yes, that does make the .rst file be internally consistent, so
Reviewed-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>
Tested-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx>

It's interesting that the generated html always uses periods
(at least in my testing), regardless of what is used in the input
file. E.g., "A)" becomes "A." in the generated html.


> Signed-off-by: Manuel Ebner <manuelebnerli@xxxxxxxxxxx>
> ---
>  Documentation/filesystems/fuse/fuse.rst | 8 ++++----
>  1 file changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/Documentation/filesystems/fuse/fuse.rst b/Documentation/filesystems/fuse/fuse.rst
> index 0fbd5a03f..063d99959 100644
> --- a/Documentation/filesystems/fuse/fuse.rst
> +++ b/Documentation/filesystems/fuse/fuse.rst
> @@ -173,10 +173,10 @@ the error set to EINTR.
>  It is also possible that there's a race between processing the
>  original request and its INTERRUPT request.  There are two possibilities:
>  
> -  1. The INTERRUPT request is processed before the original request is
> +  1) The INTERRUPT request is processed before the original request is
>       processed
>  
> -  2. The INTERRUPT request is processed after the original request has
> +  2) The INTERRUPT request is processed after the original request has
>       been answered
>  
>  If the filesystem cannot find the original request, it should wait for
> @@ -239,9 +239,9 @@ How are requirements fulfilled?
>  
>   A) The mount owner could gain elevated privileges by either:
>  
> -    1. creating a filesystem containing a device file, then opening this device
> +    1) creating a filesystem containing a device file, then opening this device
>  
> -    2. creating a filesystem containing a suid or sgid application, then executing this application
> +    2) creating a filesystem containing a suid or sgid application, then executing this application
>  
>      The solution is not to allow opening device files and ignore
>      setuid and setgid bits when executing programs.  To ensure this

-- 
~Randy