caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: ls-ocaml-developer-2006@m-e-leypold.de
To: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] ocaml-developer mailing-list: subscribe now!
Date: Mon, 12 Mar 2007 02:49:32 +0100	[thread overview]
Message-ID: <n73b4b6xjn.fsf@hod.lan.m-e-leypold.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0703111725180.2645@droopy> (Martin Jambon's message of "Sun, 11 Mar 2007 18:28:20 -0700 (PDT)")


Martin Jambon <martin.jambon@ens-lyon.org> writes:

> On Sun, 11 Mar 2007, ls-ocaml-developer-2006@m-e-leypold.de wrote:
>
>>> 2) Skipping all the unnecessary "language geekiness" stuff
>>
>> And that cannot be done by hand so that we have to split the community?
>
> Having to do things by hand is never really a good sign.

Really? But how will the relevant mail be distributed to the
relevant lists? Aren't we deciding by hand to which list the mail goes
and isn't this prone to errors (i.e. "language geekiness" turning up
at your list and pedestrian mail turning up at caml-list)? And if the
splitting of mail by topics ("by hand") doesn't work well enough,
we'll all have to subscribe to two lists. How annoying.

> Seriously, subscribing to a mailing-list is a one-time operation,
> while deleting messages is a daily thing. O(1) wins over O(n), that's
> all.

I didn't complain about subscribing, but that there is another
list. Which will have (in my setup at least) to be sorted by the
incoming mail sorter, will have to have its own local folder/archive
and its own quirks concerning the mail headers (which are NEVER right
in lists). All that is work too.

But seriously: If you list is a success, we will have two mailing list
archives (that have to be searched for solutions) and I don't expect
we'll be able to avoid subscribing to both lists, because the scopes
of each lists can hardly be distinguished. ONE always wins over TWO,
that's all. :-)

And fragmentation hurts especially the newcomers who will often only
find and search one archive/list and then go away disapppointed (or
enraged).

And: Will the CAML weekly news editor also read you list?

Regards -- Markus


  reply	other threads:[~2007-03-12  1:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-09 20:02 Martin Jambon
2007-03-10 16:34 ` [Caml-list] " Daniel Bünzli
2007-03-10 20:32   ` Martin Jambon
2007-03-10 20:56     ` Joel Reymont
2007-03-11  3:10       ` Martin Jambon
2007-03-11 10:07         ` Gabriel Kerneis
2007-03-11 23:25           ` Richard Jones
2007-03-11 23:55             ` Oliver Bandel
2007-03-12  0:18               ` Erik de Castro Lopo
2007-03-29  0:34         ` Jon Harrop
2007-03-11 15:11     ` ls-ocaml-developer-2006
2007-03-12  1:28       ` Martin Jambon
2007-03-12  1:49         ` ls-ocaml-developer-2006 [this message]
2007-03-12  2:21           ` Martin Jambon
2007-03-12  9:25             ` ls-ocaml-developer-2006
2007-03-13 16:53               ` Nathaniel Gray

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=n73b4b6xjn.fsf@hod.lan.m-e-leypold.de \
    --to=ls-ocaml-developer-2006@m-e-leypold.de \
    --cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).