public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/32859] [4.3 Regression] "make info" fails in libiberty Date: Mon, 23 Jul 2007 17:17:00 -0000 [thread overview] Message-ID: <20070723171709.9190.qmail@sourceware.org> (raw) In-Reply-To: <bug-32859-10391@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from tkoenig at gcc dot gnu dot org 2007-07-23 17:17 ------- I currently cannot check the documentation changes requried in the review for PR 30814. The condition of a Blocker, "Blocks development and/or testing work" is fulfilled, IMHO. Andrew, you marked this as a non-blocker. How else can I check documentatin patches? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32859
next prev parent reply other threads:[~2007-07-23 17:17 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-23 6:04 [Bug other/32859] New: " tkoenig at gcc dot gnu dot org 2007-07-23 6:05 ` [Bug other/32859] " tkoenig at gcc dot gnu dot org 2007-07-23 9:23 ` pinskia at gcc dot gnu dot org 2007-07-23 17:17 ` tkoenig at gcc dot gnu dot org [this message] 2007-07-23 17:29 ` dj at redhat dot com 2007-07-23 19:47 ` tkoenig at gcc dot gnu dot org 2007-07-24 0:32 ` pinskia 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=20070723171709.9190.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).