From: Adrien Nader <adrien@notk.org>
To: Alexey Egorov <electreg@list.ru>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] ocaml compiler license
Date: Thu, 5 Mar 2015 20:41:36 +0100 [thread overview]
Message-ID: <20150305194136.GA31199@notk.org> (raw)
In-Reply-To: <1425577100.968957623@f83.i.mail.ru>
Hi,
It has been explained on the caml-list in the past that the important
part was to be able to tell the two apart if I remember correctly.
In any case, git makes it trivial to get a set of patches for you
changes so I don't see an issue there.
--
Adrien Nader
next prev parent reply other threads:[~2015-03-05 19:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 17:38 Alexey Egorov
2015-03-05 19:41 ` Adrien Nader [this message]
2015-03-05 19:50 ` Alexey Egorov
2015-03-05 23:07 ` David Allsopp
2015-03-05 23:28 ` Fabrice Le Fessant
2015-03-05 23:54 ` Milan Stanojević
2015-03-06 7:41 ` Adrien Nader
2015-03-06 8:45 ` David Allsopp
2015-03-06 9:01 ` Roberto Di Cosmo
2015-03-06 9:08 ` David Allsopp
2015-03-06 9:31 ` Roberto Di Cosmo
2015-03-06 9:41 ` David Allsopp
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=20150305194136.GA31199@notk.org \
--to=adrien@notk.org \
--cc=caml-list@inria.fr \
--cc=electreg@list.ru \
/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).