From: "Alexander Terekhov" <TEREKHOV@de.ibm.com>
To: pthreads-win32@sources.redhat.com
Subject: Re: License wars
Date: Tue, 21 Oct 2003 10:07:00 -0000 [thread overview]
Message-ID: <OF68539DD9.AFEAEFB7-ONC1256DC6.00356320-C1256DC6.00377B28@de.ibm.com> (raw)
In-Reply-To: <200310202328.h9KNSO0D017343@darkside-nh.nsw.cmis.csiro.au>
> There is no point in getting angry like that.
I do get angry because each and every "pro FSF" supporter that
I've met so far on the net, made no exception with respect to
showing it rather clearly that s/he had made zilch of research
(other than absorbing a lot of FSF propaganda and myths). Talk
to your lawyer and...
> Most recently there was a article in Forbes magazine about it.
http://groups.google.com/groups?selm=F5lN.5v.19%40gated-at.bofh.it
read this entire thread.
regards,
alexander.
next prev parent reply other threads:[~2003-10-21 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 12:45 Hugues Talbot
2003-10-20 15:01 ` Alexander Terekhov
2003-10-20 23:28 ` Hugues Talbot
2003-10-21 10:07 ` Alexander Terekhov [this message]
2003-10-20 15:10 ` Phil Frisbie, Jr.
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=OF68539DD9.AFEAEFB7-ONC1256DC6.00356320-C1256DC6.00377B28@de.ibm.com \
--to=terekhov@de.ibm.com \
--cc=pthreads-win32@sources.redhat.com \
/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).