Re: gcj on intel mac patches

[Tom Tromey <tromey at redhat dot com>]

>>>>> "Sandro" == Sandro Tolaini <tolaini@libero.it> writes:

Sandro> I have also found and patched two bugs in Classpath (in the Win32
Sandro> port). They are present even in the gcc trunk. What is the patching
Sandro> policy for them? Do you incorporate foreign patches in Classpath or
Sandro> do you only send patches to Classpath authors and sync with Classpath
Sandro> project every now and then?

Generally speaking we do most library development directly on
Classpath, and fix bugs there.  We don't usually fix pure class
library bugs on GCC's svn trunk -- instead we import and merge in the
periodic (every 2 months) Classpath releases.

Most libgcj hackers also have write access to Classpath.

Occasionally we will fix a bug on svn trunk, if it seems worthwhile.
And, on release branches we typically import patches as needed,
provided they meet the release criteria (usually: doesn't break binary
compatibility).

Sandro> Andi, I think you should be interested in these patches: they are
Sandro> related to large file support and CreateFile used for
Sandro> locking...  lucene doesn't work very well on Win32 without them! :)

Let me know what I should do.  Is your paperwork in order?  I've been
holding off on your patches until that is ready, but I confess I don't
know how far along you are.

Tom