couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benoit Chesneau <bchesn...@gmail.com>
Subject Re: splitting rcouch in multiple repo
Date Wed, 05 Feb 2014 15:56:30 GMT
On Wed, Feb 5, 2014 at 4:38 PM, Paul Davis <paul.joseph.davis@gmail.com>wrote:

> All of those repos already exist:
>
> https://git-wip-us.apache.org/repos/asf?s=couchdb


perfect

>
>
> Some but not all of those I've done the initial legwork on extracting
> source code from couch and/or rcouch. I have some time right now while
> I wait on other things to pull those at into new branches named
> something like import-rcouch.
>
> The hard part here is going to be how we merge differences in the
> couch application. The history gets fairly tricky to maintain in the
> split through the rename src/couchdb to src/couch. I'll give it a
> whirl with the approach I did for bigcouch to see if that works and
> gives the same sha's at least for the initial history.
>

ok, make sense since i have also at some point moved it to src/couch (and
will be renamed to couch_core soon in rcouch).

- benoit



>
> On Wed, Feb 5, 2014 at 9:00 AM, Benoit Chesneau <bchesneau@gmail.com>
> wrote:
> > I am seeing that bigcouch is splitting everything in its own repo. I
> could
> > also do the same for rcouch quite easily. The question is how.
> >
> > I basically need the following repo:
> >
> > couch_collate
> > couch_mrview
> > couch_index
> > couch_replicator
> > couch_httpd
> > couch_collate
> >
> > (and probably soon a couch_js)
> >
> > I think most are already existing except maybe couch_collate ( I need to
> > check).
> >
> > Is creating  merge-branch enough?
> >
> > What about the missing repositories? How to ask for them?
> >
> > - benoit
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message