public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: cygheap base mismatch detected
Date: Mon, 20 Feb 2006 05:36:00 -0000	[thread overview]
Message-ID: <20060220052656.GA26280@trixie.casa.cgf.cx> (raw)
In-Reply-To: <Pine.BSF.4.63.0602192022550.90470@m0.truegem.net>

On Sun, Feb 19, 2006 at 09:02:10PM -0800, Mark Geisert wrote:
>Forgive me for possibly reading more into your text than you intended
>and thus responding inappropriately, but, Cygwin is an all-volunteer
>and essentially non-managed project.  (No offense Christopher :-) There
>are no *guarantees* about anything.  If Cygwin works for you, that's
>great.  It is possible though that it won't work for you and for any of
>various reasons specific to each volunteer, can't or won't be made to
>work for you in any particular timeframe.

The "can't" term is likely to be operative for this particular case.

>How to present the situation to your management is something we can't
>answer.  I would say, though, perhaps your management could consider a
>Cygwin support contract with Red Hat in order to get fixes for problems
>you run into.  It might be worth it if Cygwin is truly the only way to
>accomplish your technical goals.

A Red Hat support contract is not a guarantee of a fix for every
end-user problem.  Changing Cygwin to deal with this issue, as it has
been described, is likely to not fall under normal support and would
undoubtedly require additional $$$ for development.

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/

  reply	other threads:[~2006-02-20  5:26 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-19  3:34 Dill, Jens (END-CHI)
2006-02-19 18:41 ` Yitzchak Scott-Thoennes
2006-02-20  5:26 ` Mark Geisert
2006-02-20  5:36   ` Christopher Faylor [this message]
2006-02-21 19:31 ` cygheap base mismatch detected ( Attn: rebase maintainer ) Yitzchak Scott-Thoennes
2006-02-21 20:25   ` Jason Tishler
2006-02-21 21:56 ` cygheap base mismatch detected Jason Tishler
  -- strict thread matches above, loose matches on Subject: below --
2018-03-02  8:14 ignace danneels
2018-03-02  9:39 ` Marco Atzeri
2012-07-18  0:03 Andrew DeFaria
2012-07-18  1:56 ` Reini Urban
2012-07-18  2:37   ` Andrew DeFaria
2012-07-18 15:04     ` Reini Urban
2012-07-18 18:16       ` Andrew DeFaria
2012-07-18 18:38         ` Earnie Boyd
2012-07-18 19:03           ` Andrew DeFaria
2012-02-29 21:19 Charles Wilson
2012-02-29 23:23 ` marco atzeri
2012-03-01  5:56 ` Heiko Elger
2012-03-01  7:03   ` marco atzeri
2012-03-01 10:25   ` Corinna Vinschen
2012-03-01 10:52 ` Corinna Vinschen
2012-03-01 10:59   ` marco atzeri
2012-03-01 12:15     ` Corinna Vinschen
2012-03-01 22:44       ` Charles Wilson
2012-03-02  9:00         ` Corinna Vinschen
2012-03-02 17:11           ` Charles Wilson
2006-02-21 17:40 Dill, Jens (END-CHI)
2006-02-21 16:10 Dill, Jens (END-CHI)
2006-02-21 16:37 ` Brian Dessent
2006-02-21 19:18 ` Yitzchak Scott-Thoennes
2006-02-17 22:56 Dill, Jens (END-CHI)
2006-02-17 22:33 Dill, Jens (END-CHI)
2006-02-18 14:33 ` Mark Geisert
2006-02-17 17:43 Dill, Jens (END-CHI)
2006-02-16 23:45 Dill, Jens (END-CHI)
2006-02-17 10:23 ` Dave Korn
2006-02-16 22:05 Dill, Jens (END-CHI)
2006-02-16 19:38 Dill, Jens (END-CHI)
2006-02-16 20:06 ` Chris Taylor
2006-02-16 18:36 Dill, Jens (END-CHI)
2006-02-16 19:50 ` Dave Korn
2006-02-16  8:40 Dill, Jens (END-CHI)
2006-02-16 17:57 ` Christopher Faylor
2006-02-16 18:08 ` Dave Korn
2005-04-07 10:35 Andreas Heckel
2005-04-07 13:25 ` Dave Korn
2006-02-15 23:49   ` Jens Dill
2006-02-15 23:58     ` Christopher Faylor
2006-02-16 10:42     ` Dave Korn
2005-04-08  0:10 ` Mark Hadfield
2005-04-08  7:35   ` Andreas Heckel

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=20060220052656.GA26280@trixie.casa.cgf.cx \
    --to=cgf-no-personal-reply-please@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).