bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bernhard Voelker <mail@bernhard-voelker.de>
To: Ben Pfaff <blp@cs.stanford.edu>, Eric Blake <eblake@redhat.com>
Cc: Paul Eggert <eggert@cs.ucla.edu>, bug-gnulib <bug-gnulib@gnu.org>
Subject: Re: close() behavior when there are multiple fds for a socket
Date: Fri, 22 Oct 2021 00:02:11 +0200	[thread overview]
Message-ID: <4f3faec5-3bb3-dd0b-5d82-144decbbe1d1@bernhard-voelker.de> (raw)
In-Reply-To: <CAA_G9+jp_2D7+is5KZiuXgePxFi4_csuTo=RsbR5zOUSe9p4PA@mail.gmail.com>

On 10/15/21 20:41, Ben Pfaff wrote:
> On Fri, Oct 15, 2021 at 11:40 AM Eric Blake <eblake@redhat.com> wrote:
>> On Fri, Oct 15, 2021 at 09:10:04AM -0700, Ben Pfaff wrote:
>>> What a bureaucratic organization! The bug report form, once I got a login,
>>> requires one to specify a page number and line number, but it seems that
>>> you can only get the PDF version of the spec that has that information  if
>>> you belong to an organization that is a member, so I filled those in with "?"
>>> and am hoping for the best.
>>
>> That's fine.  Adding page numbers after the fact is something that
>> happens rather frequently; and I've done in for your bug in particular
>> just now.
> 
> Thanks so much!

Would you mind adding the opengroup bug here for reference?

Thanks & have a nice day,
Berny


  reply	other threads:[~2021-10-21 22:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 23:03 close() behavior when there are multiple fds for a socket Ben Pfaff
2021-10-14 23:09 ` Paul Eggert
2021-10-14 23:53   ` Ben Pfaff
2021-10-14 23:55     ` Paul Eggert
2021-10-15 16:10       ` Ben Pfaff
2021-10-15 18:40         ` Eric Blake
2021-10-15 18:41           ` Ben Pfaff
2021-10-21 22:02             ` Bernhard Voelker [this message]
2021-10-21 22:53               ` Ben Pfaff

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://lists.gnu.org/mailman/listinfo/bug-gnulib

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

  git send-email \
    --in-reply-to=4f3faec5-3bb3-dd0b-5d82-144decbbe1d1@bernhard-voelker.de \
    --to=mail@bernhard-voelker.de \
    --cc=blp@cs.stanford.edu \
    --cc=bug-gnulib@gnu.org \
    --cc=eblake@redhat.com \
    --cc=eggert@cs.ucla.edu \
    /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).