From: Christopher Faylor <cgf-rcm@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygwinb19.dll
Date: Thu, 04 Sep 2003 14:17:00 -0000 [thread overview]
Message-ID: <20030904141739.GC13532@redhat.com> (raw)
In-Reply-To: <OFE7921B5D.01D3DCF1-ONC1256D97.004CDE9E-C1256D97.004D42AA@diamond.philips.com>
On Thu, Sep 04, 2003 at 04:02:11PM +0200, jurgen.defurne wrote:
>Yes, Christopher, I know. I was just trying to get some more
>information or maybe a quick fix. In this case I think it is better
>that the more we know, the better we can defend ourselves against
>people who try make us pay licenses, based upon 5 year old products,
>which have perfectly well successors.
Let me make it really clear again: If you are using software distributed
by some other entity then you go to them for help. I'm sorry (really!)
that you are having problems but they are not *my* problems to solve and
they are not problems that this mailing list can be used to solve. It
is unreasonable to expect that a high traffic mailing list like this one
could be used as back channel support for an unrelated release. It is
also questionable whether discussing a DLL released in 1998 is useful
here either.
No further discussion about this here, please.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2003-09-04 14:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 14:04 cygwinb19.dll jurgen.defurne
2003-09-04 14:17 ` Christopher Faylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-11-04 8:25 cygwinb19.dll jurgen.defurne
2003-11-04 8:16 cygwinb19.dll jurgen.defurne
2003-09-04 11:34 cygwinb19.dll jurgen.defurne
2003-09-04 11:45 ` cygwinb19.dll Lapo Luchini
2003-09-04 13:50 ` cygwinb19.dll Christopher Faylor
2003-09-04 11:14 cygwinb19.dll jurgen.defurne
2003-09-04 11:23 ` cygwinb19.dll Lapo Luchini
2003-09-04 11:04 cygwinb19.dll jurgen.defurne
2003-09-04 9:16 cygwinb19.dll jurgen.defurne
2003-09-04 9:48 ` cygwinb19.dll Lapo Luchini
2003-09-04 9:54 ` cygwinb19.dll Brian Dessent
[not found] <01IYYJCER1TA00004H@scottish-newcastle.co.uk>
1998-07-03 6:28 ` Cygwinb19.dll Michael Hirmke
1998-07-01 1:19 Cygwinb19.dll Robert.Cross
1998-07-01 16:23 ` Cygwinb19.dll Michael Hirmke
1998-07-02 2:30 ` Cygwinb19.dll Leo Mauro
1998-07-02 12:38 ` Cygwinb19.dll Paul Shirley
[not found] <c=GB%a=TMAILUK%p=DCNET%l=EXCHANGE2-980625102357Z-3080@smtp.datcon.co.uk>
1998-05-31 17:25 ` Cygwinb19.dll Michael Weiser
1998-05-31 17:25 Cygwinb19.dll Robert.Cross
1998-05-31 17:25 Cygwinb19.dll Robert.Cross
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=20030904141739.GC13532@redhat.com \
--to=cgf-rcm@cygwin.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).