public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/17252] getrandom and getentropy syscall Date: Mon, 11 Aug 2014 15:47:00 -0000 [thread overview] Message-ID: <bug-17252-131-zNOp4iBn6e@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-17252-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=17252 --- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> --- If you wish to propose a new API for glibc, please make the proposal on libc-alpha, taking an active lead in driving the discussion to consensus. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2014-08-11 15:47 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-10 17:04 [Bug libc/17252] New: " crrodriguez at opensuse dot org 2014-08-11 15:47 ` joseph at codesourcery dot com [this message] 2014-08-11 20:49 ` [Bug libc/17252] " fweimer at redhat dot com 2014-08-16 16:54 ` fweimer at redhat dot com 2014-10-06 13:38 ` alex.gaynor at gmail dot com 2015-02-24 14:21 ` victor.stinner at gmail dot com 2015-02-24 14:34 ` crrodriguez at opensuse dot org 2015-08-14 14:17 ` nmav 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-17252-131-zNOp4iBn6e@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).