public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "schwinge-bugzilla-sources dot redhat dot com at nic-nac-project dot de" <sourceware-bugzilla@sources.redhat.com> To: glibc-bugs@sources.redhat.com Subject: [Bug libc/765] New: libio/fmemopen.c: trunk change needed on glibc-2_3-branch Date: Fri, 25 Feb 2005 10:18:00 -0000 [thread overview] Message-ID: <20050225101816.765.schwinge-bugzilla-sources.redhat.com@nic-nac-project.de> (raw) #v+ 2005-02-02 Alfred M. Szmidt <ams@gnu.org> [...] * libio/fmemopen.c: Include <stdint.h>. #v- -- Summary: libio/fmemopen.c: trunk change needed on glibc-2_3- branch Product: glibc Version: 2.3.4 Status: NEW Severity: normal Priority: P2 Component: libc AssignedTo: gotom at debian dot or dot jp ReportedBy: schwinge-bugzilla-sources dot redhat dot com at nic-nac- project dot de CC: glibc-bugs at sources dot redhat dot com GCC build triplet: i386-pc-gnu GCC host triplet: i386-pc-gnu GCC target triplet: i386-pc-gnu http://sources.redhat.com/bugzilla/show_bug.cgi?id=765 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2005-02-25 10:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-25 10:18 schwinge-bugzilla-sources dot redhat dot com at nic-nac-project dot de [this message] 2005-02-25 10:20 ` [Bug libc/765] " schwinge-bugzilla-sources dot redhat dot com at nic-nac-project dot de 2005-03-01 4:02 ` gotom at debian dot or dot jp 2005-03-01 20:57 ` cvs-commit at gcc dot gnu dot org 2005-03-01 20:58 ` roland at gnu dot org 2005-03-15 8:10 ` jakub 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=20050225101816.765.schwinge-bugzilla-sources.redhat.com@nic-nac-project.de \ --to=sourceware-bugzilla@sources.redhat.com \ --cc=glibc-bugs@sources.redhat.com \ /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).