From: "Sébastien Hinderer" <Sebastien.Hinderer@inria.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Ask questions on the mailing lists too
Date: Wed, 19 Jan 2022 16:54:43 +0100 [thread overview]
Message-ID: <Yeg0Q/I7coB6C67Q@prajna.paris.inria.fr> (raw)
In-Reply-To: <87k0eyadsv.fsf@m4x.org>
Hey Alan,
Many thanks for your response.
Alan Schmitt (2022/01/17 10:53 +0100):
> Hello Sébastien,
>
> On 2022-01-17 10:20, Sébastien Hinderer <Sebastien.Hinderer@inria.fr> writes:
>
> > Being myself blind I feel very concerned about accessibility. I admin I
> > didn't try the forum, but (1) all the forums I tried so far I ofudn way
> > mess accessible than good old mailing lists and (2) yes, mailing lists
> > are totally accessible and, in my opinion, very simple to use.
> > Many thanks for promoting the accessibility concern!
>
> The OCaml forum has a mailing list mode (this is how I read it):
As mentionned, I am not able to enable that mode on my own. I may ask
for help for this step, I just wanted to let people know.
> All posts are sent as email messages, preserving a thread structure. One can
> also reply to a post by email. This mode must be set as a preference on
> the site to be activated. There are limitations, however: edited
> messages are not resent (so it’s impossible to know what the edit was),
> and I think quotes are not preserved when replying to messages (I should
> recheck that).
Is it possible to start a thread by e-mail (not just to respond to
existing threads).
> Following both this mailing list and the forum, I have to say there is
> much more activity going on there nowadays.
I was assuming that the forum was more promoted than the list and that
this difference was the exmlanation. Well things may be the other way
around, and now I suspect they actually happen in both directions.
Sébastien.
next prev parent reply other threads:[~2022-01-19 15:54 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
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 [this message]
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=Yeg0Q/I7coB6C67Q@prajna.paris.inria.fr \
--to=sebastien.hinderer@inria.fr \
--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