Does anyone have any experience with git subtree on this list? I was under the impression that as long as you ensured that it was a strict copy of upstream it was fairly simple.
For your list of repos to keep separate, those sound fine to me regardless of subtree. They're all fairly stable at this point and I agree at least plausibly usable outside CouchDB. On Wed, Apr 13, 2016 at 11:30 AM, Alexander Shorin <[email protected]> wrote: > Hi Paul! > > Thanks for great input! > > On Wed, Apr 13, 2016 at 7:11 PM, Paul Davis <[email protected]> > wrote: >> If anyone has a strong objection to a monolithic Erlang repo I'd like >> to hear it. Otherwise I may work up a lengthier and more thorough >> proposal for dev@ to consider consolidating all of these repositories >> for sanity and profit. > > It's hard to object against that since this actually solves a lot of > problems solution of which will require more work to do and still will > leave a place for mistakes or require quite specific toolchain to > work. > > Making our current repos design work right will require even more work to > apply. > > So, for point of time/resources/usability there is no much choice. > > I think folding the "Erlang repos developed by ASF" list will solve > most part of the problems. However, I think it worth to keep these > apps in own repos: > - rexi > - b64url > - config > - snappy > - khash > - ets-lru > - twig (why we still need it?) > > As they could be reused outside and they shouldn't involve any > dependencies with other couch modules by design. Everyone else may > stand on where they are. > > P.S. I'm not sure if git-subtree will not introduce more new problems > as it's quite tricky thing to live with it. > > -- > ,,,^..^,,,
