Hi Patrick,

On 9/6/22 13:58, Patrick Reader wrote:
> On 06/09/2022 12:50, Alejandro Colomar wrote:
>> Would you mind fixing those small issues and send an v2?
> 
> Voilà!
> 
>  From a63c099d31c8fd27af6428c4d9191df698b2c0e7 Mon Sep 17 00:00:00 2001
> From: Patrick Reader <_@pxeger.com>
> Date: Tue, 6 Sep 2022 12:56:12 +0100
> Subject: [PATCH 2/2] fix formatting

I was going to apply your patches, when I got a warning from git-am(1):

warning: Patch sent with format=flowed; space at the end of lines might 
be lost.
Applying: unshare.2: Add note about potential capabilities confusion
error: corrupt patch at line 10

I guess you copied the patches into your mailer, and it screwed it.  If 
you could re-send your patches with git-send-email(1) or some other tool 
that can send them pristine, that would be great.  Otherwise, I can try 
to apply your changes manually.

Cheers,

Alex

> 
> ---
>   man/man2/unshare.2 | 7 ++++---
>   1 file changed, 4 insertions(+), 3 deletions(-)
> 
> diff --git a/man/man2/unshare.2 b/man/man2/unshare.2
> index 851129022..79a960728 100644
> --- a/man/man2/unshare.2
> +++ b/man/man2/unshare.2
> @@ -464,9 +464,10 @@ Such functionality may be added in the future, if 
> required.
>   .PP
>   Creating all kinds of namespace, except user namespaces, requires the
>   .B CAP_SYS_ADMIN
> -capability. However, since creating a user namespace automatically 
> confers a
> -full set of capabilities, creating both a user namespace and any other 
> type
> -of namespace in the same
> +capability.
> +However, since creating a user namespace automatically confers a full 
> set of
> +capabilities,
> +creating both a user namespace and any other type of namespace in the same
>   .BR unshare ()
>   call does not require the
>   .B CAP_SYS_ADMIN

-- 
Alejandro Colomar
<http://www.alejandro-colomar.es/>