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

Re: [MirageOS-devel] Permission to Absorb mirage-http

  • To: Rudi Grinberg <rudi.grinberg@xxxxxxxxx>
  • From: Anil Madhavapeddy <anil@xxxxxxxxxx>
  • Date: Thu, 25 May 2017 07:14:27 +0100
  • Cc: "mirageos-devel@xxxxxxxxxxxxxxxxxxxx" <mirageos-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Thu, 25 May 2017 06:14:35 +0000
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=recoil.org; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; q=dns; s= selector1; b=FjAreYw6Y1yJdPAaAhG0vTdnL+nshNyPhSdzZT+fgnzoZR+iEx2 H1zX4xiRzsI48qkHuKqnba5j1Nb0gEZ7atXuHlLk0SLMEXjgv8YV3EyiFmPjeS0g yHtSCtIqSTMfoUk54WImUj7u2UWEvx3HOuIiGkm/I1SYzpUab0X8QIeo=
  • List-id: Developer list for MirageOS <mirageos-devel.lists.xenproject.org>

On 25 May 2017, at 07:03, Rudi Grinberg <rudi.grinberg@xxxxxxxxx> wrote:
> As you all know, the recent switch to jbuilder makes it far easier to
> maintain multiple opam packages out of a single repo. So this is a
> chance to re-evaluate some of the repository organization decisions made
> earlier on.
> One such example is mirage-http [1]. This is a library that is tightly
> bound to the internals of cohttp and provides the same kind of
> functionality that cohttp does itself. Moreover, it doesn't have any of
> its own documentation. That suggests that it fails to meet the bar for
> its own git history. Therefore, I propose that we simply move it back to
> the main cohttp repository. Note that I will preserve mirage-http's git
> history in this process.

I agree.  There is also 

MirageOS-devel mailing list



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