From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: cygwin gcc DLLs loaded by Visual C++ crashing - SOLVED
Date: Thu, 14 Feb 2002 16:35:00 -0000 [thread overview]
Message-ID: <20020215003558.GM6876@redhat.com> (raw)
In-Reply-To: <001c01c1b5b5$cc7062f0$2801a8c0@dcuthbert2k>
On Fri, Feb 15, 2002 at 09:14:56AM +0900, Dylan Cuthbert wrote:
>It surely doesn't matter if we aren't distributing our code to anyone
>other than ourselves, otherwise you've probably got millions of
>offenders of the GPL.
Right. If you're only using it internally, you don't have to worry
about the GPL.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
prev parent reply other threads:[~2002-02-15 0:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-13 2:57 cygwin C++ DLLs and inter-operation with M$OFT Dylan Cuthbert
2002-02-13 7:37 ` Larry Hall (RFK Partners, Inc)
2002-02-13 19:06 ` cygwin gcc DLLs loaded by Visual C++ crashing Dylan Cuthbert
2002-02-13 22:09 ` cygwin gcc DLLs loaded by Visual C++ crashing - SOLVED Dylan Cuthbert
2002-02-14 7:23 ` Christopher Faylor
2002-02-14 16:14 ` Dylan Cuthbert
2002-02-14 16:35 ` Christopher Faylor [this message]
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=20020215003558.GM6876@redhat.com \
--to=cgf@redhat.com \
--cc=cygwin@cygwin.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).