On 31/05/21 14.38, Chris Packham wrote:
Is your problematic repo public? If so, we can test against that.
Unfortunately not. It's actually an internal kernel tree which has a
different root to upstream (hence using git replace to attach upstream).
All of which make the history a bit funky.
I don't know if the problem will survive anonymisation but I can try.
Did you mean vendor kernel tree based on Linux kernel? I think you can
try reproducing the issue with either Linus' tree [1] (mainline only) or
Greg's stable tree [2] (mainline + release branches and tags).
[1]: https://github.com/torvalds/linux
[2]: https://github.com/gregkh/linux
--
An old man doll... just what I always wanted! - Clara
