On Mon, 13 Jul 2020 14:55:15 -0000, GitLab Bridge on behalf of Justin Forbes wrote: > This tree is literally based on Linus' up to date tree, upstream > commit-id's don't exist in patches because if they have the upstream > commit id, the patch no longer applies. I'm not sure I follow - of course the patches are not in Linus's tree but there are in some other maintainer's tree, right? As such, they do have a commit id (albeit not necessarily a stable one, depending on the maintainer; even a commit id that is going to change is still good enough for review, though). There were rare cases of maintainers not using git but keeping a series of patches manually; is it the case here? Also, the submission policy explicitly requires patches to contain upstream status and a commit id, so this shouldn't be surprising: https://cki-project.gitlab.io/kernel-ark/submitting-contributions.html#upstream-status Jiri _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx
