public inbox for glibc-bugs-regex@sourceware.org help / color / mirror / Atom feed
From: "msebor at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs-regex@sourceware.org Subject: [Bug regex/28170] attribute access (write_only, 4, 3) on regexec triggers a warning Date: Fri, 13 Aug 2021 21:54:09 +0000 [thread overview] Message-ID: <bug-28170-132-LdRDK5WDfw@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28170-132@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28170 --- Comment #1 from Martin Sebor <msebor at gmail dot com> --- Patch: https://sourceware.org/pipermail/libc-alpha/2021-August/130137.html -- You are receiving this mail because: You are on the CC list for the bug.
prev parent reply other threads:[~2021-08-13 21:54 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-02 19:57 [Bug regex/28170] New: " msebor at gmail dot com 2021-08-13 21:54 ` msebor at gmail dot com [this message]
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-28170-132-LdRDK5WDfw@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs-regex@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).