public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Larry Hall <lh-no-personal-replies-please@cygwin.com>
To: Stephane Donze <donze@exalead.com>, Brian Bruns <bruns@2mbit.com>
Cc: cygwin@cygwin.com
Subject: Re: "Hyperthreading" problems
Date: Sun, 02 Jan 2005 19:19:00 -0000	[thread overview]
Message-ID: <6.2.0.14.0.20050102135824.02f6f278@pop.prospeed.net> (raw)
In-Reply-To: <41D71156.9000705@exalead.com>

At 04:08 PM 1/1/2005, you wrote:
>Brian Bruns wrote:
>>
>><rant>
>>I think you really really really need to reevaluate what you say
>>before you hit send.
>>
>>The open source/free software developers that I communicate with/work
>>with wrote the stuff they did because they needed an
>>application/library/script for a specific need, and decided to release
>>the software to the public in the hope that someone else might find it
>>useful, and the hope that other people might contribute back.
>> 
>
>That's exactly my point: what I was trying to say is that Cygwin wants and deserves to be more than a project developped for a specific need and released to the public "as is". An to be more than that, it needs to have an active "technical support", that cannot expect users to fix bugs by themselves.
>
>


<snip>


>In fact, Cygwin *does* sell licenses: http://www.redhat.com/software/cygwin/ .


Ah good.  So you have seen that there is already at least one response to 
your assertion above.  Obviously, if one expects to be able to demand action
on a particular issue, one has to have "bought" such a right.  The link you
provide above is one method of buying the right to demand.  I expect there
are others folks on this list that would entertain the notion of fixing 
problems for compensation too, so that's another option for anyone 
interested.  I don't think anyone here would argue that there isn't some need 
for such fee-based support avenues.  And you can see by the link you provide 
that Red Hat is one such avenue.  The thing to remember is that this list is 
not a fee-based services, which has it's benefits and it's detriments.  One
detriment is there's really no leverage that a user has to demand support.
But one can ask. ;-)



--
Larry Hall                              http://www.rfk.com
RFK Partners, Inc.                      (508) 893-9779 - RFK Office
838 Washington Street                   (508) 893-9889 - FAX
Holliston, MA 01746                     


--
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/

  reply	other threads:[~2005-01-02 19:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <41D1D2B2.4030200@exalead.com>
2004-12-28 22:29 ` Stephane Donze
2004-12-28 23:15   ` Christopher Faylor
2004-12-29  0:50   ` Brian Bruns
2005-01-01 21:07     ` Stephane Donze
2005-01-02 19:19       ` Larry Hall [this message]
2004-12-29  1:26   ` Brian Dessent
2004-12-29  1:51     ` Christopher Faylor
2004-12-29 15:33       ` Volker Bandke
2004-12-28 22:53 Robb, Sam
  -- strict thread matches above, loose matches on Subject: below --
2004-12-28 22:50 Bakken, Luke
2004-12-24  8:01 Stéphane Donzé
2004-12-24 15:50 ` Christopher Faylor

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=6.2.0.14.0.20050102135824.02f6f278@pop.prospeed.net \
    --to=lh-no-personal-replies-please@cygwin.com \
    --cc=bruns@2mbit.com \
    --cc=cygwin@cygwin.com \
    --cc=donze@exalead.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).