From: orbifx <fox@orbitalfox.eu>
To: Gabriel Scherer <gabriel.scherer@gmail.com>,
Sam Kuper <sampablokuper@posteo.net>,
caml-list@inria.fr
Subject: Re: [Caml-list] Ask questions on the mailing lists too
Date: Tue, 18 Jan 2022 09:48:51 +0000 [thread overview]
Message-ID: <696b25b0-7567-0b1b-4203-9f53634ca998@orbitalfox.eu> (raw)
In-Reply-To: <CAPFanBG5eR-uFpQwd-73yRkmCxUdiYgzO4JS+ggBRM__rDey4Q@mail.gmail.com>
Gabriel, thank you for clarifying how this initiative came about. It's insightful.
Sam, you are making a valiant effort, but I doubt it's doing anything, most people have made up their minds.
Which brings to the point, that some people got to chose both what parameters constitute a good solution and the solution. I recognise it's their initiative and they can execute it as they wish and suits, but room must be left for others' preferences and their initiatives.
Mailing list and Discourse should now run in parallel and if people choose the list they shouldn't be diverted to the forum. Thus the word "too" in the subject.
next prev parent reply other threads:[~2022-01-18 9:49 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 18:56 [Caml-list] Type Error in OCaml Code mukesh tiwari
2022-01-15 21:18 ` Nicolás Ojeda Bär
2022-01-16 9:40 ` [Caml-list] Ask questions on the mailing lists too orbifx
2022-01-16 14:31 ` Sam Kuper
2022-01-17 9:20 ` Sébastien Hinderer
2022-01-17 9:33 ` Daniil Baturin
2022-01-17 14:30 ` Sam Kuper
2022-01-17 14:56 ` Daniil Baturin
2022-01-17 17:36 ` Sam Kuper
2022-01-17 21:06 ` Gabriel Scherer
2022-01-18 1:51 ` Sam Kuper
2022-01-19 15:46 ` Sébastien Hinderer
2022-01-18 9:48 ` orbifx [this message]
2022-01-18 15:55 ` Simon Cruanes
2022-01-19 16:31 ` Sébastien Hinderer
2022-01-19 17:51 ` Sam Kuper
2022-01-19 18:09 ` Sam Kuper
2022-01-19 19:09 ` Sébastien Hinderer
2022-01-19 20:53 ` Sam Kuper
2022-01-19 18:42 ` Simon Cruanes
2022-01-19 19:03 ` Sébastien Hinderer
2022-01-19 20:50 ` Sam Kuper
2022-01-20 20:56 ` Edwin Török
2022-03-11 8:46 ` Sébastien Hinderer
2022-03-11 9:37 ` Vasilis Goumas
2022-03-11 9:42 ` Gabriel Scherer
2022-01-19 15:33 ` Sébastien Hinderer
2022-01-19 21:43 ` Gabriel Scherer
2022-01-19 22:01 ` Sam Kuper
2022-01-19 22:38 ` Sébastien Hinderer
[not found] ` <50AF4FEF-5CD6-40E7-9FA3-78814CBEE230@etorok.eu>
2022-01-17 22:47 ` Sam Kuper
2022-01-17 9:53 ` Alan Schmitt
2022-01-17 13:52 ` Sam Kuper
2022-01-19 15:18 ` Sébastien Hinderer
2022-01-19 15:54 ` Sébastien Hinderer
2022-01-20 9:12 ` Alan Schmitt
[not found] ` <87pmom7sz7.fsf@m4x.org>
2022-01-20 14:15 ` Sébastien Hinderer
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=696b25b0-7567-0b1b-4203-9f53634ca998@orbitalfox.eu \
--to=fox@orbitalfox.eu \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=sampablokuper@posteo.net \
/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).