public inbox for
 help / color / mirror / Atom feed
From: "Jon Beniston" <>
To: <>
Subject: Re: libgcj for win32
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <004201bf605a$389894b0$> (raw)
In-Reply-To: <>

----- Original Message -----
From: Jeff Sturm <>
To: Anthony Green <>
Cc: <>; <>
Sent: 16 January 2000 17:56
Subject: Re: libgcj for win32

> On Sun, 16 Jan 2000, Anthony Green wrote:
> > This is great Jon.  Your web site says:
> >
> > "The source code is not currently available as it is in a
> > pre-neanderthal state. It will, however, at some point in the future
> > be added in to the main libgcj distribution."
> >
> > Excellent - I would very much like patches in the main distribution.
> > However, libgcj's license (the LGPL) compels you make sources
> > available for any binary release, no matter what state they're in.
> > Can you please put them up on your site?
> For that matter, it's erroneous to assume that the patches aren't useful
> to someone in a "pre-neanderthal" state.  There are volunteers who can
> help get them ready for inclusion in libgcj, including the necessary
> autoconf hacking.

Yeah, I agree. However, I've got to convert them all to GNU style formatting
+ I have absolutley no idea how to use diff or patch! (Sorry, I aint no Unix
guru). I'll make them available very soon.


       reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <>
2000-04-01  0:00 ` Jon Beniston [this message]
2000-04-01  0:00 libgcj, Win32 & dll's Jeff Sturm
2000-04-01  0:00 ` Bryce McKinlay
2000-04-01  0:00   ` Jeff Sturm
2000-04-01  0:00     ` libgcj for win32 Jon Beniston
2000-04-01  0:00       ` Jeff Sturm
2000-04-01  0:00         ` Jon Beniston
2000-04-01  0:00           ` Jeff Sturm
2000-04-01  0:00             ` Tom Tromey

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='004201bf605a$389894b0$' \ \ \

* 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).