public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Colomar <alx.manpages@gmail.com>
To: Guy Shefy <guyshefyb@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH] setpgid.2: ERRORS: add EPERM for nonexisting process group
Date: Mon, 20 Feb 2023 16:51:53 +0100	[thread overview]
Message-ID: <d50e6acf-bf10-f72d-b04b-e0fe8b2d1f20@gmail.com> (raw)
In-Reply-To: <Y/OWxEajSbwD8UsL@T14s-004530>


[-- Attachment #1.1: Type: text/plain, Size: 760 bytes --]

Hello Guy,

On 2/20/23 16:50, Guy Shefy wrote:
> Signed-off-by: Guy Shefy <guyshefyb@gmail.com>
> ---
>   man2/setpgid.2 | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/man2/setpgid.2 b/man2/setpgid.2
> index 52c5bd5fc..0b0182eb9 100644
> --- a/man2/setpgid.2
> +++ b/man2/setpgid.2
> @@ -214,6 +214,11 @@ a session leader
>   .RB ( setpgid (),
>   .BR setpgrp ()).
>   .TP
> +.B EPERM
> +The target process group does not exists.
> +.RB ( setpgid (),
> +.BR setpgrp ()).
> +.TP

Could you please document how you found this in the commit message?

Thanks,

Alex

>   .B ESRCH
>   For
>   .BR getpgid ():

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-02-20 15:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-20 15:50 [PATCH] setpgid.2: ERRORS: add EPERM for nonexisting process group Guy Shefy
2023-02-20 15:51 ` Alex Colomar [this message]
2023-02-20 16:01   ` Guy Shefy
2023-02-20 16:08     ` Guy Shefy
2023-02-25  1:01       ` Alex Colomar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d50e6acf-bf10-f72d-b04b-e0fe8b2d1f20@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=guyshefyb@gmail.com \
    --cc=linux-man@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox