From: Tom Tromey <tromey@redhat.com>
To: Adam Megacz <gcj@lists.megacz.com>
Cc: java@gcc.gnu.org
Subject: Re: apologies, 3.1, mingw wishlist
Date: Tue, 09 Apr 2002 15:36:00 -0000 [thread overview]
Message-ID: <87pu18ebws.fsf@creche.redhat.com> (raw)
In-Reply-To: Adam Megacz's message of "09 Apr 2002 15:20:20 -0700"
>>>>> "Adam" == Adam Megacz <gcj@lists.megacz.com> writes:
Adam> Second: is 3.1 still scheduled for release on 15-Apr, or has it
Adam> been pushed back?
I assume it has been pushed back but I have not heard either official
or unofficial word.
Adam> - Fix the badly-broken notifyAll()
Adam> - Make Win32Process work
Adam> - Hash Synchronization (this already works, I just have to merge patches)
Adam> - Closer review of java.io.* for proper error handling
These all sound great.
Depending on timing, etc, they might not make it into 3.1. That isn't
fatal. We could always get the changes into 3.1.1.
Adam> - Get the testsuite to run (somehow -- not sure yet how I'll do it)
AG suggests using Wine. Anything that works is fine by me though.
Adam> Is there anything else that I should consider?
You know the Windows status better than anybody. How about submitting
a PR for all the problems and missing things you know of once you've
finished the next round of coding? That way we'll have a better idea
of the state and to-do items later on.
Tom
next prev parent reply other threads:[~2002-04-09 22:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 15:29 Adam Megacz
2002-04-09 15:36 ` Tom Tromey [this message]
2002-04-09 17:50 ` Brian Jones
2002-04-11 10:57 ` Adam King
2002-04-11 12:52 ` apologies, 3.1, mingw wishlist [okay to add new ctor to ConcreteProcess?] Adam Megacz
2002-04-11 15:20 ` Tom Tromey
2002-04-11 15:53 ` Java debugger Adam King
2002-04-11 17:28 ` Nic Ferrier
2002-04-11 17:36 ` Bryce McKinlay
2002-04-11 23:13 ` apologies, 3.1, mingw wishlist [okay to add new ctor to ConcreteProcess?] Adam Megacz
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=87pu18ebws.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=gcj@lists.megacz.com \
--cc=java@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).