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

[MirageOS-devel] What was the reasoning for splitting out mirage-http?


Back in 2013, mirage-http was extracted out of cohttp into itâs own repository. Although Iâm ignorant of how the decision was made, I understand that there could have been good reasons for this a couple of years ago. Today, however, it seems like thereâs less good reasons for such a split. Now that opam supports multiple packages out of the same repo and since weâre planning on releasing cohttp backends as their own packages [1], maybe it makes sense to treat mirage-http the same way?

The reason why Iâm bringing this up now is that the current situation does have the disadvantage of confusing users and creating possibly unnecessary churn for maintainers [2]



MirageOS-devel mailing list



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