caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Vasilis Goumas <bgoumas@gmail.com>
To: "Sébastien Hinderer" <Sebastien.Hinderer@inria.fr>,
	"Edwin Török" <edwin+ml@etorok.net>,
	caml-list@inria.fr
Subject: Re: [Caml-list] Ask questions on the mailing lists too
Date: Fri, 11 Mar 2022 09:37:56 +0000	[thread overview]
Message-ID: <CAF0KdiNW0LW2Z7oYzYGd46jjfP=WkqJ+VwSbV_h0m2mtvyfG5w@mail.gmail.com> (raw)
In-Reply-To: <YisMTlJhdIjtOsm2@prajna.paris.inria.fr>

[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]

Hi all,

sorry for asking here, but it might be relevant with the topic of asking
questions. I am unable to unsubscribe from this
mailing list. I have tried sending unsubscribe at least 5 times, none of
them work. How can I unsubscribe?

Best,
Bill

On Fri, Mar 11, 2022 at 8:46 AM Sébastien Hinderer <
Sebastien.Hinderer@inria.fr> wrote:

> Dear Edwin,
>
> I am very sorry for this late response.
>
> I wanted to thank you for allthe work you have done and the nice script
> you came up with. It will not only be useful, it will also be a nice
> starting point to learn Python and REST stuff.
>
> One of the reasons it took me so long to respond is that I am actually a
> bit scared of enabling this mailing-list mode, fearing to receive even
> more e-mails that will slow me down even more.
>
> So, the situation is that, so far, I didn't dare to even try your script
> and I apologize for that. Be sure, though, that I'll keep your e-mail
> preciously, both for the case I'd need to run the script, and also to
> use it as a basis for learning.
>
> Best wishes,
>
> Sébastien.
>

[-- Attachment #2: Type: text/html, Size: 1515 bytes --]

  reply	other threads:[~2022-03-11  9:38 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 [this message]
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='CAF0KdiNW0LW2Z7oYzYGd46jjfP=WkqJ+VwSbV_h0m2mtvyfG5w@mail.gmail.com' \
    --to=bgoumas@gmail.com \
    --cc=Sebastien.Hinderer@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=edwin+ml@etorok.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).