public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rmbeer2 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/29445] Error in the documentation of OPEN
Date: Thu, 04 Aug 2022 00:39:32 +0000	[thread overview]
Message-ID: <bug-29445-131-TW8x2wDpB5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29445-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=29445

rm beer <rmbeer2 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Error in the documentation  |Error in the documentation
                   |                            |of OPEN

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  reply	other threads:[~2022-08-04  0:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-04  0:37 [Bug libc/29445] New: Error in the documentation rmbeer2 at gmail dot com
2022-08-04  0:39 ` rmbeer2 at gmail dot com [this message]
2022-08-04  8:01 ` [Bug libc/29445] Error in the documentation of OPEN fweimer at redhat dot com

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=bug-29445-131-TW8x2wDpB5@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).