caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Till Varoquaux <till.varoquaux@gmail.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] STOP (was: Search for the smallest possible possible Ocaml segfault)
Date: Thu, 08 Nov 2007 18:55:54 +0100	[thread overview]
Message-ID: <47334DAA.80407@inria.fr> (raw)
In-Reply-To: <9d3ec8300711080617g1b023711o1a8f9aa50b7874@mail.gmail.com>

Guys,

Before posting this kind of messages, I'd like you to stop for a
second and think about what you're doing.  The answer is: a disservice
to the Caml community.  (This also applies to most of Skaller's rants
and some of Harrop's marketing, by the way.)

Yes, OCaml has bugs, like all software of this complexity -- and
probably a lot less than your own software.  Be supportive and
cooperative: post bug reports with repro cases where they belong, on
the bug tracking system, and let us developers handle them the way we
see fit.

That kind of snickering posts is neither helpful nor supportive.  What
benefits do you expect from trashing Caml in public?  Especially since
most of you never paid any cent for it, and some of you make a living
out of it.

> My impression was that bug reported via the mail ling list were
> acknowledged faster, I'm putting this theory to the test.

You've just demonstrated out that this practice is very effective at
pissing me off.  Are you satisfied?

- Xavier Leroy


  parent reply	other threads:[~2007-11-08 17:55 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 14:17 Search for the smallest possible possible Ocaml segfault Till Varoquaux
2007-11-08 15:00 ` [Caml-list] " Jean-Christophe Filliâtre
2007-11-08 15:17   ` Till Varoquaux
2007-11-08 15:55     ` Adrien
2007-11-08 16:05 ` Alain Frisch
2007-11-08 16:30   ` Feature request (was Re: [Caml-list] Search for the smallest possible possible Ocaml segfault....) Martin Jambon
2007-11-08 18:23     ` Martin Jambon
2007-11-08 16:07 ` [Caml-list] Search for the smallest possible possible Ocaml segfault Jeremy Yallop
2007-11-08 16:11   ` Jeremy Yallop
2007-11-08 16:17     ` Till Varoquaux
2007-11-08 17:02       ` Stefano Zacchiroli
2007-11-08 17:10         ` Till Varoquaux
2007-11-08 17:02       ` Pascal Zimmer
2007-11-08 17:12         ` Oliver Bandel
2007-11-08 17:11 ` Oliver Bandel
2007-11-08 17:13 ` Zheng Li
2007-11-08 17:55 ` Xavier Leroy [this message]
2007-11-08 18:11   ` [Caml-list] STOP (was: Search for the smallest possible possible Ocaml segfault) Tom Primožič
2007-11-08 18:23     ` [Caml-list] STOP Robert Fischer
2007-11-08 19:01       ` Basile STARYNKEVITCH
2007-11-08 18:31   ` [Caml-list] STOP (was: Search for the smallest possible possible Ocaml segfault) Till Varoquaux
2007-11-08 19:06   ` Oliver Bandel
2007-11-09 18:09     ` Pierre Weis
2007-11-10 14:32       ` OCaml's formatting libraries Bünzli Daniel
2007-11-10 14:58         ` [Caml-list] " Jon Harrop
2007-11-10 15:43           ` Bünzli Daniel
2007-11-10 19:13             ` Jon Harrop
2007-11-13  9:22               ` Pierre Weis
2007-11-13  9:13             ` Pierre Weis
2007-11-13  8:53         ` Pierre Weis

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=47334DAA.80407@inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=till.varoquaux@gmail.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 NNTP newsgroup(s).