public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rob1weld at aol dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcj/31890] Java Namespace error - javaprims.h out of sync Date: Tue, 15 May 2007 04:29:00 -0000 [thread overview] Message-ID: <20070515042913.29740.qmail@sourceware.org> (raw) In-Reply-To: <bug-31890-13830@http.gcc.gnu.org/bugzilla/> ------- Comment #2 from rob1weld at aol dot com 2007-05-15 05:29 ------- Thanks. If someone with write-access runs the script and tosses the result into the SVN I'll consider this bug resolved (for me). I changed severity to minor. The maintainers _might_ want to update the "Makefile maintainer scripts" (or whatever scripts you use to test GCC prior to sending in your changes to the SVN) so that the script gets ran when changes are made to the appropriate files (don't forget the check_jni_methods.sh problem while your there :) ). -- rob1weld at aol dot com changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|major |minor http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31890
next prev parent reply other threads:[~2007-05-15 4:29 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-10 5:37 [Bug java/31890] New: " rob1weld at aol dot com 2007-05-14 19:57 ` [Bug java/31890] " tromey at gcc dot gnu dot org 2007-05-15 4:29 ` rob1weld at aol dot com [this message] 2008-08-04 13:52 ` [Bug libgcj/31890] " rob1weld at aol dot com 2008-08-04 18:53 ` tromey at gcc dot gnu dot org 2008-08-05 1:31 ` tromey at gcc dot gnu dot org 2008-08-05 15:47 ` doko 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=20070515042913.29740.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).