public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jun dot w dot hz at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug manual/10038] one web page per node documents navigator line incorrect in section 3.x. Date: Tue, 07 Apr 2009 09:02:00 -0000 [thread overview] Message-ID: <20090407090224.1972.qmail@sourceware.org> (raw) In-Reply-To: <20090407090029.10038.jun.w.hz@gmail.com> ------- Additional Comments From jun dot w dot hz at gmail dot com 2009-04-07 09:02 ------- According to http://www.gnu.org/software/libc/manual/html_node/index.html The top line of http://www.gnu.org/software/libc/manual/html_node/Locking-Pages.html#Locking-Pages and http://www.gnu.org/software/libc/manual/html_node/Resizing-the-Data-Segment.html#Resizing-the-Data-Segment and http://www.gnu.org/software/libc/manual/html_node/Memory-Allocation.html#Memory-Allocation should be modified. Section '3.4 Locking Pages' doesn't have a 'next'. Section '3.3 Resizing the Data Segment' should have a next of 'Locking-Pages'. The next of Section '3.2 Allocating Storage For Program Data' should be 'Resizing the Data Segment', not 'Locking Pages'. -- What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |minor http://sourceware.org/bugzilla/show_bug.cgi?id=10038 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2009-04-07 9:02 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-04-07 9:01 [Bug manual/10038] New: " jun dot w dot hz at gmail dot com 2009-04-07 9:02 ` [Bug manual/10038] " jun dot w dot hz at gmail dot com 2009-04-07 9:02 ` jun dot w dot hz at gmail dot com [this message] [not found] <bug-10038-131@http.sourceware.org/bugzilla/> 2012-09-07 0:08 ` jsm28 at gcc dot gnu.org 2014-07-01 7:21 ` fweimer 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=20090407090224.1972.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).