Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Dave Berry <dave@kal.com>
To: Markus Mottl <mottl@miss.wu-wien.ac.at>,
	Pierre Weis <Pierre.Weis@inria.fr>
Cc: OCAML <caml-list@inria.fr>
Subject: RE: Newsgroup for Caml?
Date: Thu, 15 Jun 2000 10:22:00 +0100	[thread overview]
Message-ID: <3145774E67D8D111BE6E00C0DF418B662503C5@nt.kal.com> (raw)

The comp.lang.ml newsgroup is gatewayed to and from the ML mailing list.
These were set up to discuss all dialects of ML (that's why the newsgroup is
called comp.lang.ml instead of comp.lang.sml, and the same for the mailing
list).  So you wouldn't be "seizing power", you would be like lost sheep
returning to the fold.  The number of postings would clearly show which
implementation is the more active.

Dave.


-----Original Message-----
From: Markus Mottl [mailto:mottl@miss.wu-wien.ac.at]
Sent: Wednesday, June 14, 2000 12:19 AM
To: Pierre Weis
Cc: OCAML
Subject: Re: Newsgroup for Caml?


On Tue, 13 Jun 2000, Pierre Weis wrote:
> > Don't you think that we should create a newsgroup for Caml? There is a
lot
> > of messages in this mailing list, and perhaps it could be a way to make
Caml
> > known? Do you have an opinion about that?
> 
> I'm 100% pro :)
> 
> Pierre Weis [as the moderator of the Caml list.]

That's understandable ;-)

I wouldn't mind using a newsgroup. However, there is already one called
"comp.lang.ml", which has very low traffic: seems that people who are
interested in OCaml (= not SML) have all signed up to the mailing list... :)

Instead of creating a new one, the more imperialistically minded among us
might choose to seize power over there...

But I think that the volume on our list is acceptably high to open a
separate newsgroup. This would definitely lead to much more publicity.  The
direct comparison of traffic on both newsgroups would then also allow
people to recognize the better choice ;)

Best regards,
Markus Mottl

-- 
Markus Mottl, mottl@miss.wu-wien.ac.at, http://miss.wu-wien.ac.at/~mottl




             reply	other threads:[~2000-06-15 11:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-15  9:22 Dave Berry [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-16 18:41 Brent Fulgham
2000-06-19 10:24 ` Jean-Francois Monin
2000-06-15 13:32 Dave Berry
2000-06-15 12:31 Damien Doligez
2000-06-13 17:02 Dave Berry
2000-06-14  7:18 ` Sven LUTHER
2000-06-12 19:05 Daniel de Rauglaudre
2000-06-13 16:53 ` Pierre Weis
2000-06-13 23:18   ` Markus Mottl
2000-06-15  3:07     ` Jacques Garrigue
2000-06-15 11:29       ` Pierre Weis
2000-06-15 12:53         ` Benjamin C. Pierce
2000-06-15 20:36           ` Michael Vanier
2000-06-15 12:22       ` Markus Mottl
2000-06-16  8:01       ` Sven LUTHER
2000-06-14  8:08   ` Jean-Yves Moyen
2000-06-13 19:16 ` Michael Vanier
2000-06-15 13:47 ` Xavier Leroy
2000-06-16  8:07   ` Niall Dalton
2000-06-16 16:44     ` Daniel de Rauglaudre
2000-06-16  8:32   ` Jacques Garrigue
2000-06-16 11:25   ` Alexander I. Zhezherun

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=3145774E67D8D111BE6E00C0DF418B662503C5@nt.kal.com \
    --to=dave@kal.com \
    --cc=Pierre.Weis@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=mottl@miss.wu-wien.ac.at \
    /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