From: Don Zickus on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_545998171 @hertonrk-rh - see my above answer to @jmflinuxtx. I have pondered on/off the last few months about how to eliminate the whole 'merge-base' selection as I don't like it and requires git history to run CI (which increases time and uses network bandwidth which isn't always free). I don't have a good answer yet as each attempted solution uncovers more ugly 'master' dependencies and more hacks. :-( And yes, using the 'marker' file was going to be my hard-coded 'merge-base' answer. So I am stuck with moving forward today. My main motivation is to update the docs in !772 but that requires handling the 'upstream' fallout. If I thought I could remove 'merge-base' in a reasonable way, I would go that way instead. But I am struggling to implement something that works. Again I am stuck: short term fix or long term fix. Thoughts? Help? _______________________________________________ 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
