caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Adrien Nader <adrien@notk.org>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [RFC] Remaining changes for cross-compilation support in OCaml
Date: Fri, 21 Feb 2014 08:19:20 +0100	[thread overview]
Message-ID: <20140221071920.GB7924@notk.org> (raw)
In-Reply-To: <20140220110343.GA22692@frosties>

On Thu, Feb 20, 2014, Goswin von Brederlow wrote:
> On Tue, Feb 18, 2014 at 07:50:32PM +0100, Adrien Nader wrote:
> > Hi,
> > 
> > Roughly one year ago, late Wojciech Meyer and I started working on the
> > integration of a set of patches aimed at enabling the OCaml compiler to
> > be used for cross-compilation.
> > 
> > Some of the patches so far have caused issues to some people. The goal
> > of this RFC and email thread is to raise awareness of the upcoming work
> > and its implications and also to start getting feedback as early as
> > possible. The patches should be handled through the github interface
> > which Gabriel Scherer mentionned a few weeks ago.
> 
> Seeing as you want to use the github interface to submit patches I
> assume you also have a fully functioning branch on github that people
> could try. Would be nice to give the URL for that (or to make such a
> branch).

No, no public branch right now.
In the past, I have had to play catch up with the trunk.
I started with a set of patches, two months later I could start having
some integrated, meanwhile trunk had changed and most of the patches had
to be updated; by the time I could update the patches, trunk would have
moved again enough to require a new update and so on. Moreover, some
patches require a new approach and this is reason I sent this RFC.

I'm not yet sure how I will be pushing them. I think I will probably
push the WIP stuff on http://cgit.notk.org and mostly use github for the
code review stuff. That WIP stuff will also be pushed to and rebased
with no consideration for anyone: it will be a copy of my local repo, no
matter which state it is in.
(NB: rebases is very useful because bootstrapping creates new binaries
of several MBs)

In any case, I'll send a message to the list when the first code is
there and slightly usable.

-- 
Adrien Nader

  reply	other threads:[~2014-02-21  7:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-18 18:50 Adrien Nader
2014-02-19  9:51 ` [Caml-list] [RFC] Remaining changes for cross-compilation support oleg
2014-02-20 11:03 ` [Caml-list] [RFC] Remaining changes for cross-compilation support in OCaml Goswin von Brederlow
2014-02-21  7:19   ` Adrien Nader [this message]
2014-02-20 16:53 ` Xavier Leroy
2014-02-21  0:06   ` Anil Madhavapeddy
2014-02-21  7:06     ` Adrien Nader
2014-02-21  1:44   ` Francois Berenger
2014-02-21  7:53   ` Adrien Nader
2014-02-21 11:56     ` Benoît Vaugon
2014-02-21 12:52       ` Mark Shinwell
2014-02-22 14:17         ` Adrien Nader
2014-02-22 14:30       ` Adrien Nader
2014-02-22 15:16         ` Gabriel Kerneis
2014-02-22 20:24           ` Richard W.M. Jones

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=20140221071920.GB7924@notk.org \
    --to=adrien@notk.org \
    --cc=caml-list@inria.fr \
    --cc=goswin-v-b@web.de \
    /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).