Assuming this is all ASLv2 code, there shouldn't be anything that prevents Harmony committers from patching code from Android's class library to Harmony's class library, correct? I don't know if this would complicate things even more or not, but it would certainly allow for Harmony to benefit from any improvements in a more timely fashion.
-Nathan On Mon, Dec 29, 2008 at 1:34 PM, Dan Bornstein <[email protected]> wrote: > I can't answer the procedural questions you raise, but I can add this: > > On Fri, Dec 26, 2008 at 2:55 PM, Aleksey Shipilev > <[email protected]> wrote: >> I volunteer to publish the diffs between Android's classlib and >> Harmony, but we need to clarify these legal issues first. As the >> background: as Android uses the classlib from 2007-04-11, there some >> technical difficulty -- the Harmony classlib was updated a lot :) >> >> >> "Android vs. Harmony-2007-04-11": >> (line counts): 67689 total lines to merge > > The Android core library folks have been spending a lot of time lately > trying to bring the core library sources up to date with respect to > the last year and a half of Harmony development. It's not clear which > branch of the Android code you diffed against, but the latest work in > this regard is in the recently released "cupcake" branch. We are > working on getting it all merged back to the mainline, and we are also > working on getting more changes into the branch from our private > repository. (Eventually, we expect to work on this stuff completely in > the open, but we are still in transition.) > > <http://android.git.kernel.org/?p=platform/dalvik.git;a=tree;h=refs/heads/cupcake;hb=cupcake> > > -dan >
