> > > However, I understand that you prefer to have primary authorship, even if > > the > > code has been re-organized in new commits, moved, modified or rewritten. > > Correct.
For anyone working in this area that is intending to upstream anything from asahi, I think if code is rewritten completely it's probably not consistent to keep the primary author. Copyright doesn't cover ideas, it covers the code. It's fine to add acknowledgements and other tags. For all the other cases where it's just moving code around or modifying it, please try and retain the primary author. I'd suggest if anyone is basing stuff on the Asahi tree, they try to take things as-is as closely as possible, then use subsequent commits to clean/fix/rework, this might mean we have to live with some messy history that isn't easily bisectable, but I think to avoid any confusion later and to keep from repeatedly bothering Lina with kernel development questions on what is acceptable for what patches, we should try to remain consistent here. If you write new code from scratch without reference to the asahi tree at all, please try and state this is a clean implementation to avoid future possible confusions, if you are aware there is asahi code, though I realise that could be contradictory. There are often cases where there is only one way to write some code and I'd rather we don't fall into unwarranted accusations of bad behaviour. Dave.
