public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "roland at gnu dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug manual/1506] Memory leak in sample code for LIST_, TAILQ_, and CIRCLEQ_REMOVE Date: Sun, 23 Oct 2005 01:03:00 -0000 [thread overview] Message-ID: <20051023010344.5984.qmail@sourceware.org> (raw) In-Reply-To: <20051020161442.1506.dleppik@vocalabs.com> ------- Additional Comments From roland at gnu dot org 2005-10-23 01:03 ------- You can file an enhancement bug on the manual that the header and its macros should be documented. But the most effective thing will be to contribute some documentation to the manual. This is far from the highest priority for improving the libc manual, and there is nearly no volunteer time available for working on the manual. -- http://sourceware.org/bugzilla/show_bug.cgi?id=1506 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
prev parent reply other threads:[~2005-10-23 1:03 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-10-20 16:14 [Bug manual/1506] New: " dleppik at vocalabs dot com 2005-10-20 16:19 ` [Bug manual/1506] " jakub at redhat dot com 2005-10-20 16:43 ` dleppik at vocalabs dot com 2005-10-23 1:03 ` roland at gnu dot org [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=20051023010344.5984.qmail@sourceware.org \ --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: 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).