From: Jan Nieuwenhuizen <janneke@gnu.org>
To: Jason Haas <jhaas@www.linuxppc.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [Announce] Absoft interested in making Fortran compiler -- needs user feedback
Date: Wed, 13 Oct 1999 01:35:42 +0200 [thread overview]
Message-ID: <199910122335.BAA00876@appel.flower> (raw)
In-Reply-To: Your message of "Tue, 12 Oct 1999 17:34:27 CDT." <Pine.LNX.4.04.9910121733400.27363-100000@www.linuxppc.org>
On Tuesday, 12 October 1999, Jason Haas writes:
> On Wed, 13 Oct 1999, Jan Nieuwenhuizen wrote:
>
> > On Tuesday, 12 October 1999, Jason Haas writes:
> >
> > > We have been asked to assist Absoft, makers of the #1 commercial Linux/x8
+ 6
> > > Fortran compiler, in determining if there is a market for their product o
+ n
> > > the Linux/PowerPC platform.
> >
> > What's the licence? It sounds awfully proprietary, and a lot of us
> > are not interested at all in proprietary software.
>
> Note the word commercial.
Yes, I did. AbiWord, eg, is commercial too, yet GPL licenced.
> > I would very much appreciate it, if non-free announcements were
> > prominently marked 'non-free', or 'proprietary'.
>
> It is commercial software, although not an announcement for it -- it was
> an announcement trying to gauge interest in it.
Ok. But same thing, I would be interested in another fortran compiler,
but not if it would be proprietary.
Greetings,
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien/ | http://www.lilypond.org/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-12 23:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-12 18:18 [Announce] Absoft interested in making Fortran compiler -- needs user feedback Jason Haas
1999-10-12 22:28 ` Jan Nieuwenhuizen
1999-10-12 22:34 ` Jason Haas
1999-10-12 23:35 ` Jan Nieuwenhuizen [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-10-13 4:06 jeramy b smith
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=199910122335.BAA00876@appel.flower \
--to=janneke@gnu.org \
--cc=jhaas@www.linuxppc.org \
--cc=linuxppc-dev@lists.linuxppc.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 NNTP newsgroup(s).