From: Herton R. Krzesinski on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_545205029 I think adding origin/master would help. But it always exists, so may be it's not the behavior you want here, to show an error/force the developer to setup an upstream remote or master branch. If I understood, the problem is a stale origin/master in a developer's fork could cause issues. The same problem though happens if someone forgets to fetch upstream remote too (or update the local master branch). The logic on the Makefiles is also hard to follow regarding the upstream merges, may be it would be easier if for each upstream merge done an variable could be passed on the command line that should point to the updated MARKER instead of using merge-base and a complex logic as is today, but that's not something for this MR, could be looked later. _______________________________________________ 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 Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
