public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drepper.fsp at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/5666] when getline fails it still allocates a buffer
Date: Sun, 18 Dec 2011 01:47:00 -0000 [thread overview]
Message-ID: <bug-5666-131-1uwxKlNAim@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-5666-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=5666
Ulrich Drepper <drepper.fsp at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
--- Comment #5 from Ulrich Drepper <drepper.fsp at gmail dot com> 2011-12-18 01:46:44 UTC ---
If you want the documentation to be changed send a patch. This has nothing to
do with this bug. Don't reopen it.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next prev parent reply other threads:[~2011-12-18 1:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-5666-131@http.sourceware.org/bugzilla/>
2011-12-09 16:18 ` svoboda at cert dot org
2011-12-18 1:47 ` drepper.fsp at gmail dot com [this message]
2012-01-03 21:32 ` svoboda at cert dot org
2014-04-02 9:26 ` vapier at gentoo dot org
2014-04-03 22:24 ` cvs-commit at gcc dot gnu.org
2014-04-03 22:24 ` vapier at gentoo dot org
2014-07-02 7:45 ` fweimer at redhat dot com
2008-01-24 21:00 [Bug libc/5666] New: " werner_hahn at yahoo dot de
2008-01-24 21:04 ` [Bug libc/5666] " drepper at redhat dot com
2008-01-25 9:33 ` werner_hahn at yahoo dot de
2008-03-04 18:35 ` drepper 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-5666-131-1uwxKlNAim@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--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: 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).