IMHO it would be a pity if we lost the Git history of changes made to the Blink repository since the time that it was forked from Flink.
If the Blink repository is a true fork, i.e., branch at a certain time/commit id, from the Flink repository, then there is no problem. The entire Blink repository could be folded in to the Flink repository, simply because it actually *is* the Flink repository. Someone with access to both repositories would point to the tips of each of the Blink repository branches to bring in, and Git push them into the Flink repository one by one. If the Blink repository was taken as a source code snapshot at some point in time/commit id, then it should be fairly easy to locate the precise commit id within the Flink repository that the snapshot was taken of, and then the Blink repository can be rebased on top of that commit id. Both these sorts of repository merge operations could be experimented on by someone with access to both repositories, on their private machines, without pushing the results to the Apache Flink repository. It's only the push to Apache that is actually 'publishing' the changes to the world, and that involves the appropriate licensing searches/permission requests/approvals. Thanks, Peter -- Sent from: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/
