Re: [PATCH] ovl: fix reStructuredText syntax errors in documentation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Dec 8, 2016 at 9:49 AM, Amir Goldstein <amir73il@xxxxxxxxx> wrote:
> - Fix broken long line block quote
> - Fix missing newline before bullets list
> - Use correct numbered list syntax
>

Ping.

Neil,
I found these syntax errors when I posted your page on my wiki:
https://github.com/amir73il/overlayfs/wiki/Overlayfs-overview

Not sure if this patch should go through Miklos's tree or John's tree,
but is surely needs the ACK from you.

Thanks,
Amir.

> Signed-off-by: Amir Goldstein <amir73il@xxxxxxxxx>
> ---
>  Documentation/filesystems/overlayfs.txt | 7 ++++---
>  1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/filesystems/overlayfs.txt b/Documentation/filesystems/overlayfs.txt
> index fb6f307..634d03e 100644
> --- a/Documentation/filesystems/overlayfs.txt
> +++ b/Documentation/filesystems/overlayfs.txt
> @@ -66,7 +66,7 @@ At mount time, the two directories given as mount options "lowerdir" and
>  "upperdir" are combined into a merged directory:
>
>    mount -t overlay overlay -olowerdir=/lower,upperdir=/upper,\
> -workdir=/work /merged
> +  workdir=/work /merged
>
>  The "workdir" needs to be an empty directory on the same filesystem
>  as upperdir.
> @@ -118,6 +118,7 @@ programs.
>
>  seek offsets are assigned sequentially when the directories are read.
>  Thus if
> +
>    - read part of a directory
>    - remember an offset, and close the directory
>    - re-open the directory some time later
> @@ -137,12 +138,12 @@ When renaming a directory that is on the lower layer or merged (i.e. the
>  directory was not created on the upper layer to start with) overlayfs can
>  handle it in two different ways:
>
> -1) return EXDEV error: this error is returned by rename(2) when trying to
> +1. return EXDEV error: this error is returned by rename(2) when trying to
>     move a file or directory across filesystem boundaries.  Hence
>     applications are usually prepared to hande this error (mv(1) for example
>     recursively copies the directory tree).  This is the default behavior.
>
> -2) If the "redirect_dir" feature is enabled, then the directory will be
> +2. If the "redirect_dir" feature is enabled, then the directory will be
>     copied up (but not the contents).  Then the "trusted.overlay.redirect"
>     extended attribute is set to the path of the original location from the
>     root of the overlay.  Finally the directory is moved to the new
> --
> 2.7.4
>
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux FS]     [Yosemite Forum]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Device Mapper]     [Linux Resources]

  Powered by Linux