From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@sympa.inria.fr Delivered-To: caml-list@sympa.inria.fr Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by sympa.inria.fr (Postfix) with ESMTPS id 491D17F860 for ; Fri, 21 Feb 2014 08:19:22 +0100 (CET) Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of adrien@notk.org) identity=pra; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible Received-SPF: Pass (mail3-smtp-sop.national.inria.fr: domain of adrien@notk.org designates 91.121.71.147 as permitted sender) identity=mailfrom; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="adrien@notk.org"; x-conformance=sidf_compatible; x-record-type="v=spf1" Received-SPF: None (mail3-smtp-sop.national.inria.fr: no sender authenticity information available from domain of postmaster@nautica.notk.org) identity=helo; client-ip=91.121.71.147; receiver=mail3-smtp-sop.national.inria.fr; envelope-from="adrien@notk.org"; x-sender="postmaster@nautica.notk.org"; x-conformance=sidf_compatible X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AhgFAC39BlNbeUeT/2dsb2JhbABZgwY7gwhSvUKBDhZ0giUBAQUjVhALGAICBRMOAgIPBRgxiByrRKFEF4EpjFkRAVAHgm81gRQEmDMBgTKQdYMuO4E1 X-IPAS-Result: AhgFAC39BlNbeUeT/2dsb2JhbABZgwY7gwhSvUKBDhZ0giUBAQUjVhALGAICBRMOAgIPBRgxiByrRKFEF4EpjFkRAVAHgm81gRQEmDMBgTKQdYMuO4E1 X-IronPort-AV: E=Sophos;i="4.97,517,1389740400"; d="scan'208";a="49897313" Received: from nautica.notk.org ([91.121.71.147]) by mail3-smtp-sop.national.inria.fr with ESMTP/TLS/ADH-AES256-SHA; 21 Feb 2014 08:19:21 +0100 Received: by nautica.notk.org (Postfix, from userid 1003) id 9C3F5C009; Fri, 21 Feb 2014 08:19:20 +0100 (CET) Date: Fri, 21 Feb 2014 08:19:20 +0100 From: Adrien Nader To: Goswin von Brederlow Cc: caml-list@inria.fr Message-ID: <20140221071920.GB7924@notk.org> References: <20140218185032.GA20593@notk.org> <20140220110343.GA22692@frosties> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20140220110343.GA22692@frosties> User-Agent: Mutt/1.5.21 (2010-09-15) Subject: Re: [Caml-list] [RFC] Remaining changes for cross-compilation support in OCaml 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