public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "grgoffe at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/30647] build of gcc midi-dssi fails
Date: Sun, 11 Feb 2007 06:13:00 -0000 [thread overview]
Message-ID: <20070211061310.2847.qmail@sourceware.org> (raw)
In-Reply-To: <bug-30647-14023@http.gcc.gnu.org/bugzilla/>
------- Comment #14 from grgoffe at yahoo dot com 2007-02-11 06:13 -------
Subject: Re: build of gcc midi-dssi fails
Tom,
Thanks for your help and the info.
Any time you need to test something just let me know, I'll help if I can.
Regards,
George...
--- tromey at gcc dot gnu dot org <gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #13 from tromey at gcc dot gnu dot org 2007-02-10 07:32 -------
> The changes in your working tree should be identical to what I checked in.
> 'svn update' will notice this and do the right thing.
> You can verify this with "svn status libjava/classpath".
> It ought to report no changes.
>
>
> --
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30647
>
> ------- You are receiving this mail because: -------
> You reported the bug, or are watching the reporter.
>
=====
_/_/_/_/ _/_/_/_/ _/_/_/_/ _/_/_/ _/_/_/_/ _/_/_/_/ -----
_/ _/ _/ _/ _/ _/ _/ _/
_/ _/_/ _/_/_/_/ _/ _/ _/_/_/ _/ _/_/ _/_/_/_/ -----
_/ _/ _/ _/ _/ _/ _/ _/ _/ _/
_/_/_/_/ _/_/_/_/ _/_/_/_/ _/ _/ _/_/_/_/ _/_/_/_/ -----
"It's not what you know that hurts you, It's what you know that ain't so." Will
Rogers
____________________________________________________________________________________
Yahoo! Music Unlimited
Access over 1 million songs.
http://music.yahoo.com/unlimited
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30647
prev parent reply other threads:[~2007-02-11 6:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-30 23:01 [Bug java/30647] New: " grgoffe at yahoo dot com
2007-01-30 23:03 ` [Bug java/30647] " grgoffe at yahoo dot com
2007-02-01 9:26 ` [Bug libgcj/30647] " pinskia at gcc dot gnu dot org
2007-02-01 9:34 ` pinskia at gcc dot gnu dot org
2007-02-08 20:21 ` tromey at gcc dot gnu dot org
2007-02-09 0:19 ` grgoffe at yahoo dot com
2007-02-09 0:51 ` tromey at gcc dot gnu dot org
2007-02-09 3:34 ` grgoffe at yahoo dot com
2007-02-09 18:45 ` grgoffe at yahoo dot com
2007-02-09 19:29 ` grgoffe at yahoo dot com
2007-02-09 20:54 ` tromey at gcc dot gnu dot org
2007-02-09 20:56 ` tromey at gcc dot gnu dot org
2007-02-09 20:56 ` cvs-commit at developer dot classpath dot org
2007-02-10 1:19 ` grgoffe at yahoo dot com
2007-02-10 7:32 ` tromey at gcc dot gnu dot org
2007-02-11 6:13 ` grgoffe at yahoo dot com [this message]
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=20070211061310.2847.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=java-prs@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: link
Be 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).