public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "John.Tobey at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug manual/13542] New: carg() incorrectly documented branch cut Date: Sun, 25 Dec 2011 07:38:00 -0000 [thread overview] Message-ID: <bug-13542-131@http.sourceware.org/bugzilla/> (raw) http://sourceware.org/bugzilla/show_bug.cgi?id=13542 Bug #: 13542 Summary: carg() incorrectly documented branch cut Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: manual AssignedTo: roland@gnu.org ReportedBy: John.Tobey@gmail.com Classification: Unclassified Created attachment 6132 --> http://sourceware.org/bugzilla/attachment.cgi?id=6132 Patch to fix documentation of carg() family's branch cut manual/arith.texi gives an incorrect location for carg()'s branch cut since commit 7a68c94a5b8fb8 of 13 Jul 1998. Documentation patch attached. Kind regards, John -- 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 reply other threads:[~2011-12-25 7:38 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-12-25 7:38 John.Tobey at gmail dot com [this message] 2012-09-07 2:55 ` [Bug manual/13542] " allan at archlinux dot org 2014-06-27 11:20 ` 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=bug-13542-131@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: 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).