couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bob Dionne <>
Subject Re: questions about some commits on external libs
Date Sat, 10 Nov 2012 10:59:56 GMT
Hi Benoit,

I made that ibrowse commit. I'm not sure what the process is with respect to pushing this
upstream. At Cloudant we maintain  a fork of ibrowse that also seems to track couchdb changes
to ibrowse as well. I'm happy to handle it however you see fit.

I think this is where the rebar component based approach works well. It enables independent
development of the components. Switching to a newer version is just changing a line in rebar.config


On Nov 10, 2012, at 3:17 AM, Benoit Chesneau <> wrote:

> Hi all,
> While reviewing the code and working on the otp version of couchdb I
> have found some changes in mochiweb that I am not sure if they are
> available upstream or not and if they have been proposed:
> ibrowse:
> and maybe others. Can someone tell me if these commits are available
> upstream or if any effort in pushing them exists?
> If we really need these changes what would be the policy to apply on
> that topic. Should we fork the upstream repo and maintain our own?
> Also would be good if next time the commit message reflect the status
> of this patch vs the upstream version.
> - benoƮt

View raw message