[elbe-devel] [PATCH v2] docs/elbe-pbuilder: fix typos

[torben.hohn at linutronix.de]

On Fri, Jan 24, 2020 at 08:27:57AM +0100, yegorslists at googlemail.com wrote:
> From: Yegor Yefremov <yegorslists at googlemail.com>
> 
> Reviewed-by: Bastian Germann <bage at linutronix.de>
> Signed-off-by: Yegor Yefremov <yegorslists at googlemail.com>

please reorder...

Signed-off-by above Reviewed-by.

also please just remove the paragraph about 3.0 quilt.
this information is not true anymore, and we support uploading orig
files.

> ---
> Changes v1 -> v2:
>   - drop article before 'program' (Bastian Germann)
> 
>  docs/elbe-pbuilder.txt | 16 ++++++++--------
>  1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/docs/elbe-pbuilder.txt b/docs/elbe-pbuilder.txt
> index f0a470931..bd93941a8 100644
> --- a/docs/elbe-pbuilder.txt
> +++ b/docs/elbe-pbuilder.txt
> @@ -20,9 +20,9 @@ DESCRIPTION
>  Creates a pbuilder for a specified project and builds the Debian package
>  like pbuilder, but for the configured ELBE project.
>  
> -Currently only the source formats 3.0 (git) and 3.0 (native) are supported.
> -3.0 (quilt) requires Files in the parent directory, which are not uploaded,
> -because only the curent Workdirectory is uploaded.
> +Currently, only the source formats 3.0 (git) and 3.0 (native) are supported.
> +3.0 (quilt) requires Files in the parent directory, which are not uploaded
> +because only the current Workdirectory is uploaded.

so... please just remove this paragraph.
and add the reviewed-by tag.

>  
>  OPTIONS
>  -------
> @@ -40,7 +40,7 @@ OPTIONS
>  --cpuset <int>::
>  	When this value is not -1 (the default), the pbuilder is run using
>  	'taskset <cpuset>' which allows to limit the number of cpus used
> -	for the build. This is usefule when multithreading and qemu-user
> +	for the build. This is useful when multithreading and qemu-user
>  	yield problem with e.g. java.
>  
>  --profile string::
> @@ -59,9 +59,9 @@ A pbuilder environment for the given project or xml File will be created.
>  
>  Build the 'Debianized Project' in the current working directory. (A valid
>  ./debian directory needs to exist.) If --project was specified, the specified
> -build environment will be used. If --xmlfile is specified a new build
> -environment will be created for the given ELBE XML File and the 'Debianized
> -Project' in the current working directory will be build. The result of the
> +build environment will be used. If --xmlfile is specified, a new build
> +environment will be created for the given ELBE XML File, and the 'Debianized
> +Project' in the current working directory will be built. The result of the
>  package build is stored in ../ like pbuilder does.
>  
>  EXAMPLES
> @@ -82,7 +82,7 @@ EXAMPLES
>  --------
>  
>  * Use the pbuilder we have built, to build 'program', using the prj
> -  File generated in parent directory. And dont use more than one CPU
> +  File generated in parent directory. And don't use more than one CPU
>    as a workaround for qemu-user and java problems.
>  +
>  --------
> -- 
> 2.17.0
> 
> 
> _______________________________________________
> elbe-devel mailing list
> elbe-devel at linutronix.de
> https://lists.linutronix.de/mailman/listinfo/elbe-devel