public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "carlos at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/25895] Add __nonnull ((1)) to fopen declaration Date: Thu, 18 Apr 2024 15:52:35 +0000 [thread overview] Message-ID: <bug-25895-131-CXh7REexZh@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25895-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25895 Carlos O'Donell <carlos at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Document fopen with |Add __nonnull ((1)) to |pathname == NULL |fopen declaration CC| |carlos at redhat dot com -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-04-18 15:52 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-29 14:52 [Bug libc/25895] New: Document fopen with pathname == NULL marxin.liska at gmail dot com 2020-04-29 15:26 ` [Bug libc/25895] " schwab@linux-m68k.org 2020-04-29 16:37 ` marxin.liska at gmail dot com 2020-05-04 18:11 ` marxin.liska at gmail dot com 2020-05-09 8:02 ` mliska at suse dot cz 2024-04-18 15:52 ` carlos at redhat dot com [this message] 2024-04-18 15:53 ` [Bug libc/25895] Add __nonnull ((1)) to fopen declaration carlos 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-25895-131-CXh7REexZh@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: linkBe 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).