public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "manu at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/33768] splay-tree.c typo Date: Sat, 19 Jan 2008 00:52:00 -0000 [thread overview] Message-ID: <20080119003955.18135.qmail@sourceware.org> (raw) In-Reply-To: <bug-33768-14259@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from manu at gcc dot gnu dot org 2008-01-19 00:39 ------- Subject: Bug 33768 Author: manu Date: Sat Jan 19 00:39:08 2008 New Revision: 131650 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=131650 Log: 2008-01-19 Manuel Lopez-Ibanez <manu@gcc.gnu.org> PR other/33768 * splay-tree.c (rotate_left): Fix minor typo in comment. (rotate_right): Likewise. Modified: trunk/libiberty/ChangeLog trunk/libiberty/splay-tree.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33768
next prev parent reply other threads:[~2008-01-19 0:40 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-10-13 21:13 [Bug other/33768] New: " george at houseofellery dot com 2008-01-19 0:52 ` manu at gcc dot gnu dot org [this message] 2008-01-19 5:20 ` [Bug other/33768] " manu at gcc dot gnu dot org
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=20080119003955.18135.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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).