public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: Packaging software built with cygwin
Date: Wed, 05 Feb 2003 20:43:00 -0000	[thread overview]
Message-ID: <20030205204415.GA30513@redhat.com> (raw)
In-Reply-To: <20030205125545.A10690@thebrain.conmicro.cx>

Cutting through the noise:

1) In an open source, volunteer project there are no guarantees that
   anything will be fixed.  We do the best we can given our interests
   and time.  However, you should be reporting cygwin bugs to the cygwin
   mailing list if you want the possibility of getting them fixed.  You
   can use http://cygwin.com/bugs.html as a guide for how to submit bugs.

   No, I don't care to hear from the multitude of people in your project
   who are leaving cygwin because of all of their serious problems.  Good
   luck to them with MinGW, Interix, U/WIN, or whereever they've decided
   to use.  I'm only interested in actual bug reports.  I can do something
   with a bug report.  I can't do a single thing with "Every cygwin release
   breaks Hercules" or "Cygwin has too many bugs, so I'm giving up on it".

   I'm sure you know that neither of the above are bug reports.  They are
   basically just noise.  I don't have enough "copious spare time" to devote
   to wheedling details out of people.  YMMV.

2) I am not trying to blindside you by suggesting that you can distribute
   the Cygwin source tar ball so that Red Hat lawyers could go after you later.
   No, I'm not going to give you anything in writing.  I'm not going to
   set that precedent.  There are plenty of sites on the internet who are
   distributing the source tarballs without an official signature from Red Hat.

3) I find all GPL discussions uninteresting and unproductive.  I really really
   hope you can avoid any more harping on this.

4) I'm sorry that none of the suggestions put forth here are satisfactory
   to you.  I'm out of ideas, so that will probably be it for me in this
   thread unless there is a specific bug report that needs addressing.
   
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/

  reply	other threads:[~2003-02-05 20:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-04 22:34 Packaging software built with Cygwin Jay Maynard
2003-02-04 23:27 ` Igor Pechtchanski
2003-02-05  1:46   ` Jay Maynard
2003-02-05  2:31     ` Igor Pechtchanski
2003-02-05  2:48       ` Jay Maynard
2003-02-05  3:32         ` Packaging software built with cygwin Christopher Faylor
2003-02-05 13:38           ` Nigel Stewart & Fiona Smith
2003-02-05 14:11             ` Christopher Faylor
2003-02-05 14:14               ` Jay Maynard
2003-02-05 17:18           ` Jay Maynard
2003-02-05 17:30             ` Nigel Stewart & Fiona Smith
2003-02-05 17:52               ` Max Bowsher
2003-02-06 13:17                 ` Nigel Stewart & Fiona Smith
2003-02-06 13:43                   ` Max Bowsher
2003-02-06 14:05                     ` Nigel Stewart & Fiona Smith
2003-02-05 18:19               ` Christopher Faylor
2003-02-05 17:54             ` Christopher Faylor
2003-02-05 18:55               ` Jay Maynard
2003-02-05 20:43                 ` Christopher Faylor [this message]
2003-02-05 21:41                 ` Robert Collins
2003-02-06  9:59                 ` Ronald Landheer-Cieslak
2003-02-06 13:24                   ` Jay Maynard
2003-02-05 20:44 Franz Wolfhagen
2003-02-06 13:24 Joshua Daniel Franklin

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=20030205204415.GA30513@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).