From: Mo DeJong <mdejong@cygnus.com>
To: sourcenav@sourceware.cygnus.com
Subject: RE: Windows NT Failing on XRef Generation.
Date: Fri, 09 Feb 2001 12:01:00 -0000 [thread overview]
Message-ID: <Pine.SOL.3.91.1010209113324.22410F-100000@cse.cygnus.com> (raw)
In-Reply-To: <8F1BE54DECC1D211BB2500105A9CA42101C1C878@admin1.astralpoint>
On Fri, 9 Feb 2001, Story, Lenny wrote:
> Hmm,
>
> Ok...so ...your saying that the problem doesn't
> exist...
I don't think anyone said that.
> and you are unwilling to do anything about
> it unless i can point you directly to the issue...?
>
> If i could do that i would fix it myself.
What makes you think we would be able to do
anything about it? A bug report along
the lines of "it breaks" or "the Dr. Watson
log said instruction 0x5689384 was to blame"
is of no value. Even a stack trace can
be of little value with one of these parser
bugs. We need the source code that causes
the problem, and a small excerpt is the
best way to provide it.
> is this the kind of service we can expect if we purchase
> the product...(and service contract) from you ?
Oh, right. You mean that kind of service where people
fix bugs in free products for free. No, that is not
the kind of service you would expect in a support
contract.
> The FACT is that it does BREAK. and a core dump is more than
> enought information to find the issue.
If that were true, you would have already found the issue, no?
> This is exactly why FREE software is NOT the way to go...
> free obviously means that if it breaks your DEAD IN THE WATER....
> therefore companies cannot put any trust in them.
I don't see how a logical person could come to that
conclusion.
(Later)
> Whatever....If Redhat wants to follow the "we're not responsible for it
> model"...fine...but it affects more than just SourceNav...how are we to
> believe that they would support their embedded linux product then ? Why
> would we put it into our product, and risk the "Fix it yourself" answer
> when the product crashes....
You seem to be under the mistaken impression that slinging some
flaming emails around is going to accomplish something.
> If they aren't serious about quality, then
> what are they realling selling..?
You did download SN at no cost, right? I don't think
that qualifies as a purchase. We welcome any
help you can provide, but you have to understand
that this is not a support mailing list.
Source-Navigator is no longer a commercial
product, it is now a community project. You
can certainly pay someone to work on SN.
Red Hat engineers are available for contract
work, but you also have the option of paying
someone else to do customization.
That is kind of the point of free software.
The free in free software is about freedom,
but with that freedom comes responsibility.
Mo DeJong
Red Hat Inc
next prev parent reply other threads:[~2001-02-09 12:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-09 8:36 Story, Lenny
2001-02-09 9:57 ` Berek
2001-02-09 10:45 ` Kenneth Luke
2001-02-09 12:01 ` Mo DeJong [this message]
2001-02-09 12:27 ` Timothy M. Shead
-- strict thread matches above, loose matches on Subject: below --
2001-02-09 18:29 Story, Lenny
2001-02-09 11:41 Story, Lenny
2001-02-08 20:16 Story, Lenny
2001-02-08 20:29 ` Mo DeJong
2001-02-08 20:16 Story, Lenny
2001-02-08 16:15 Story, Lenny
2001-02-08 12:14 Story, Lenny
2001-02-08 12:25 ` Ian Roxborough
2001-02-08 9:52 dave.banham
2001-02-08 9:05 Story, Lenny
2001-02-08 9:55 ` Syd Polk
2001-02-08 11:25 ` Berek
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=Pine.SOL.3.91.1010209113324.22410F-100000@cse.cygnus.com \
--to=mdejong@cygnus.com \
--cc=sourcenav@sourceware.cygnus.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).