From: Prarit Bhargava on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1635#note_865801544 It's hard to explain. The *ONLY* reason for the last commit is to avoid the issue @jmflinuxtx hit because he executed both the old code and the new code in the same tree. If you do make dist-configs # old code # this leaves a .mismatches file (you can do a ls -l .mismatches to find it) # apply my code make -j10 dist-configs # new code # this code adds and removes .mismatches"${count}" files. The removal is done (as you noticed) with a 'rm -f .mismatches*'. However, the code (without the last commit I added) errors out by detecting '.mismatches*' -- which picks up the OLD .mismatches file. I'm not sure if that made any more sense or just confused you further. Here's the kicker: If you were now to do a 'make -j10 dist-configs' the code would return successfully because of the 'rm -f .mismatches*'. _______________________________________________ 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
