getting my stuff back into CVS

[Adam Megacz <gcj at lists dot megacz dot com>]

Hi, yall. On top of threads, I have exceptions in mingw mostly-working
now as well, so at this point I'd say the chances are "very very good"
that by my 16-Dec deadline (which has become a little bit more
flexible), I will be able to put back patches that leave mingw in a
mostly-working or completely-working state.

So it's time to think about the most efficient way of doing
this. Right now my cvs checkout is a horrid mess, so I can't really
submit my patches as I go... let me propose an alternate procedure:

Sometime in the next few days I'll reach a point where I'm mostly
satisfied with the state of mingw support. I'll then:

1. Check out a fresh copy from CVS

2. Make all the changes that I absolutely have to make to non-win32
   files and non-#ifdef-WIN32 sections in order for my stuff to
   work. Wrap this up as a patch or two (they should be very small)
   and submit it for intense scrutiny, since herein are the bits with
   the most danger of breaking stuff that was already working before I
   came along.

3. After that gets committed, I'll probably break my remaining work up
   into four or more patches:

    a. One to make mingw work without threads/execptions

    b. A second one to make threads work

    c. A third one to make exceptions work with threads

    d. Several subsequent patches to natXXX.cc as I broaden the win32
       support... the java.net/java.lang.Thread stuff will arrive
       right away, and the rest will probably keep trickling in during
       early next year.

   Again, these will be produced by manually re-making the changes in
   a fresh CVS checkout, so that the impressive amount of cruft I have
   accumulated so far won't wind up in the repository.

   Hopefully these patches won't require the same degree of scrutiny
   as (2), since most of this stuff wasn't really working when I found it.

How does this sound?

  - a