Hi, Am Donnerstag, den 21.06.2018, 16:00 -0400 schrieb Emilian Bold: > No, no, no, I want to keep the existing repository. > > Actually I just looked and there's 'git checkout --orphan' to create > a branch without a parent. > > So, we create an orphan branch, add the 2nd donation, then merge this > branch to master/. Makes sense?
I know, that I'm late to the game, but what is reason, not to do this: - branch out "second_donation_integration" - import the ZIP (I'll assume, it mostly will contain full modules) - do the cleanup work (and only that) in that donation branch - test, that this "hybrid" builds - some more motivated folks could locally merge master into that branch an see if it still works And when done, merge the cleaned-up, relicensed branch into master, at which point we'll release netbeans 9.X or netbeans 10. We then have a clear workspace for the licensing, cleanup, make it build work and have the track record how it happened. And a clear point (the merge point) where "we" decided, that the right thinks were done. Before quick hand-work starts, Geertjan has a point, that automatic mechanisms should come first. We don't gain anything if work, that automatic license replacement does, is done by humans. Greetings Matthias --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
