From: Kuba Ober <ober.14@osu.edu>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Shared run-time DLLs for commerce
Date: Mon, 7 Jan 2008 12:32:50 -0500 [thread overview]
Message-ID: <200801071232.50491.ober.14@osu.edu> (raw)
In-Reply-To: <47824B45.1000507@frisch.fr>
> 1. Distribute the source code, even without an open source license. I
> cannot imagine this would reduce your sales, but you know better.
Trolltech (of Qt fame) have been doing that since day 1 and I'm pretty sure it
has won them more business, and saved a lot of support headaches and angry
customer calls.
Cheers, Kuba
next prev parent reply other threads:[~2008-01-07 17:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 11:30 Jon Harrop
2008-01-07 13:03 ` [Caml-list] " Alain Frisch
[not found] ` <200801071503.26977.jon@ffconsultancy.com>
2008-01-07 15:54 ` Alain Frisch
2008-01-07 17:32 ` Kuba Ober [this message]
2008-01-07 19:51 ` Jon Harrop
2008-01-07 21:17 ` Stefano Zacchiroli
2008-01-08 19:39 ` Christophe TROESTLER
2008-01-08 19:42 ` Jon Harrop
2008-01-08 20:18 ` Richard Jones
2008-01-08 16:03 ` Richard Jones
2008-01-08 18:35 ` Jon Harrop
2008-01-09 9:17 ` Alain Frisch
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=200801071232.50491.ober.14@osu.edu \
--to=ober.14@osu.edu \
--cc=caml-list@yquem.inria.fr \
/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