From: Anton Bachin <antronbachin@gmail.com>
To: Thomas Refis <thomas.refis@gmail.com>
Cc: Junsong Li <ljs.darkfish@gmail.com>,
Ivan Gotovchits <ivg@ieee.org>, OCaml users <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] Namespaces – sensible file naming for OCaml projects
Date: Mon, 7 Mar 2016 16:38:57 -0600 [thread overview]
Message-ID: <F2251C99-E24E-4C15-BE16-4E1A1490C21D@gmail.com> (raw)
In-Reply-To: <CAJ_epFO10ppGts983s44q51jKX3nCekWv3VR172xAiGSeE5cVA@mail.gmail.com>
Indeed, I can confirm that Namespaces and Merlin work fine together.
Anton
> On Mar 1, 2016, at 03:25, Thomas Refis <thomas.refis@gmail.com> wrote:
>
> Hi,
>
> I haven't tested Namespaces (nice project btw) but it should work just
> fine with merlin.
>
> Thomas.
prev parent reply other threads:[~2016-03-07 22:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-29 16:40 Anton Bachin
2016-02-29 16:53 ` Arto Bendiken
2016-02-29 18:37 ` Ivan Gotovchits
2016-02-29 18:45 ` Anton Bachin
2016-03-01 1:00 ` Junsong Li
2016-03-01 9:25 ` Thomas Refis
2016-03-07 22:38 ` Anton Bachin [this message]
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=F2251C99-E24E-4C15-BE16-4E1A1490C21D@gmail.com \
--to=antronbachin@gmail.com \
--cc=caml-list@inria.fr \
--cc=ivg@ieee.org \
--cc=ljs.darkfish@gmail.com \
--cc=thomas.refis@gmail.com \
/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).