Lack of proper commits/history

Question

Lack of proper commits/history

Closed this issue 9 years ago · 4 comments

Throwing the entire kernel into one commit is less than ideal, it's difficult to see what changes were actually made. At the bare minimum e062944 should be rebased onto whichever commit BlackBerry forked the Android kernel from.

Answer 1 · 2015-11-09T18:38:03.000Z

Following the requiremetns of the GPL, files changed by BlackBerry contain a copyright notice. The commit history will not be published.

Answer 2 · 2015-11-09T18:42:17.000Z

Thanks for the tip about the copyright notice, I should be able to split the files apart properly with that.

Could you let me know approximately which commit (and repository) that this kernel was forked from? e.g., 9a1f3257d1f5013ae7dfeb8f2171b777950ab375 @ https://android.googlesource.com/device/ti/panda This isn't a requirement by the GPL, but it would save me a lot of time and I can figure it out manually if I have to.

Answer 3 · 2017-03-22T21:06:02.000Z

@Manouchehri look for CONFIG_BBRY in the source code too, those are conditionals added by Blackberry

Answer 4 · 2017-03-28T06:03:52.000Z

On a related note, here's a great example of another vendor that also crushes their Git history.

allwinner-zh/linux-3.4-sunxi#17 (comment)

I'd be willing to bet there's been a couple critical security patches applied very late or completely missed on this kernel tree. Feel free to prove me wrong.