[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[MirageOS-devel] merging charrua-{core/unix/client} repositories

  • To: mirageos-devel <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Anil Madhavapeddy <anil@xxxxxxxxxx>
  • Date: Mon, 12 Jun 2017 16:33:35 +0100
  • Delivery-date: Mon, 12 Jun 2017 15:33:49 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=recoil.org; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:cc:to; q=dns; s=selector1; b=gf+FGfXk4NlK/X1xav O/uGTlCY3IAOFsq2Qgy+py599JCayYbJ1+czVY7ejB4SRpfl4lIL9BHSejEQFrRw ICt6OzJIG2OBdyHjarsTSXZenfuHnlsIYjSgv0DseSnTdgRBp9NE6Kd3MsEYkjAe ARJUaNk38riLGktj9zhKKYmx8=
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>

In the spirit of Rudi's cohttp/mirage-http merge, I wanted to propose merging 
the Git repositories for the various Charrua implementations.  Right now we 

- charrua-core (the protocol and some server bits)
- charrua-unix (a unix daemon)
- charrua-client (a dhcpcd client)

I've ported Charrua-core to Jbuilder and am about to cut a new release, and the 
multiple OPAM packages are easy to maintain in one Git repository now (using 
topkg-jbuilder).  In return, we reduce the number of Git repositories we have 
to manage, and can collect all the issues and PRs about DHCP in one place.

So, this is primarily for Mindy and Cristiano -- would you mind if I did a PR 
that combined the various repositories into one (probably 
https://github.com/mirage/charrua) while preserving history of the individual 
existing repositories?  If there a reason for the separate existence, then 
that's fine too -- I am just on a garbage collection binge of our Git 
repositories before it gets even more out of control :-)

MirageOS-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.