unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: "Štěpán Němec" <stepnem@smrk.net>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] manual: Drop incorrect statement on PIPE_BUF and blocking writes
Date: Mon, 25 Mar 2024 12:46:47 +0100	[thread overview]
Message-ID: <87frwea5zs.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20240325085927.2041034-1-stepnem@smrk.net> ("Štěpán Němec"'s message of "Mon, 25 Mar 2024 09:59:27 +0100")

* Štěpán Němec:

> diff --git a/manual/pipe.texi b/manual/pipe.texi
> index 483c40c5c3dd..8a9a275cafe7 100644
> --- a/manual/pipe.texi
> +++ b/manual/pipe.texi
> @@ -312,8 +312,7 @@
>  
>  Reading or writing a larger amount of data may not be atomic; for
>  example, output data from other processes sharing the descriptor may be
> -interspersed.  Also, once @code{PIPE_BUF} characters have been written,
> -further writes will block until some characters are read.
> +interspersed.

Maybe “further may block” instead?  I think the reference to PIPE_BUF
and blocking could still be helpful, except that it's not a guarantee,
as you correctly point out.

Do you have copyright assignment?  If not, please add Signed-off-by: in
a second submission of the patch.

Thanks,
Florian


  reply	other threads:[~2024-03-25 11:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25  8:59 [PATCH] manual: Drop incorrect statement on PIPE_BUF and blocking writes Štěpán Němec
2024-03-25 11:46 ` Florian Weimer [this message]
2024-03-25 12:13   ` Štěpán Němec
2024-03-25 16:20     ` Zack Weinberg
2024-03-25 21:32       ` Štěpán Němec

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

  List information: https://www.gnu.org/software/libc/involved.html

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

  git send-email \
    --in-reply-to=87frwea5zs.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=stepnem@smrk.net \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).