4 ms·
Eh, after reading the mailing list this seems like an odd title. From what I gather from what I read, Intel did not want to re-license/dual-license their Apach
by gillianseed 11y ago
Eh, after reading the mailing list this seems like an odd title.
From what I gather from what I read, Intel did not want to re-license/dual-license their Apache licensed code under the 'Go-license', and the Go project want all the code in the repo to be under said 'Go-license' and won't accept it otherwise.
So blaming one party here makes no sense to me, or did I miss something ?