couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benoit Chesneau <bchesn...@gmail.com>
Subject Re: Git Repository Creation
Date Tue, 21 Jan 2014 10:37:07 GMT
On Tue, Jan 21, 2014 at 10:46 AM, Paul Davis <paul.joseph.davis@gmail.com>wrote:

> On Mon, Jan 20, 2014 at 12:05 AM, Garren Smith <garren@apache.org> wrote:
> > Thanks Paul,
> >
> > For Fauxton we just need everything that is in src/Fauxton.
> >
> > Cheers
> > Garren
> >
>


which has been moved to share/fauxton in rcouch, actually maybbe both futon
and fauxton could be provided has erlang happ with an HTTP handler and the
html/js code in priv?

- benoit

> > On 18 Jan 2014, at 3:10 AM, Paul Davis <paul.joseph.davis@gmail.com>
> wrote:
> >
> >> I've spent most of the day initializing all of our new repositories
> >> with the source code for each Erlang application. I've taken special
> >> care to make sure that we're retaining as much history as possible.
> >> I'm pretty sure that most apps are correct but we'll want to do some
> >> auditing in the future before we flip the switch in the future.
> >>
> >> The code versions are generally speaking either what's on master or on
> >> the 1843-feature-bigcouch branch. A few of them I pulled out of the
> >> 1994-merge-rcouch branch or from their respective external
> >> repositories in the case of ibrowse, mochiweb, and jiffy.
> >>
> >> Its important to note that all code was imported using a branch named
> >> "import" so that we can spend time reviewing code and possibly
> >> rewriting history before we commit to what the initial value for each
> >> repo should be. If you clone any of these repos git will be a bit
> >> confused until you switch to that branch.
> >>
> >> The couchdb-couch repo is actually a combination of what's on
> >> 1843-feature-bigcouch but is rebased against the current master so it
> >> should be all the things from both of those. I haven't investigated
> >> how much 1994-merge-rcouch has changed actual underlying code as
> >> opposed to just moved source code around so we'll have to coordinate
> >> there.
> >>
> >> We'll get the 1843-feature-bigcouch branch updated in the near future
> >> to start pulling each of these repositories directly so that people
> >> can see how that works in practice.
> >>
> >> Also of note there are currently three repos that are still empty. The
> >> couchdb-couch-collate.git, couchdb-fauxton.git, and
> >> couchdb-documentation.git are all uninitialized. For fauxton and
> >> documentation I want to hear from people that are more involved with
> >> what they'd want in there. I'm not familiar enough to be confident
> >> that I've not screwed anything up for either of those. I didn't need
> >> couch-collate but I'll get to that soonish.
> >>
> >> The other thing to point out is that Adam created a ticket in the
> >> middle of the email storm that people may want to chime in on to
> >> discuss the new commit email subject lines:
> >>
> >> https://issues.apache.org/jira/browse/COUCHDB-2032
> >
>
> Cool. I'll pull this out when I get back into my git gymnastics routine.
>

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