Weijie Yuan <wy@xxxxxxxxx> writes: > What I was trying to understand is how that fits with the particular DCO > concern being discussed here. You may never be able to tell where the AI output came from, but you can see if the updated code has resemblance to fixes we applied in the past to correct similar problems, for example. After all, you yourself without help by AI can copy our code to your patch to enhance our code, and that is perfectly legit. Take for example 5fe676f448 (t1300: remove global config settings injected by test-lib.sh, 2026年04月26日) that added test_might_fail git config --global --unset-all safe.bareRepository that clearly mimicked the tests that prepared the stage by clearing a relevant configuration variable done in an earier 313eec177a (safe.directory: allow "lead/ing/path/*" match, 2024年05月29日). By "sufficient due diligence", what I meant was that I trust Dscho well enough that he's done a similar analysis to make sure that he is copying from ourselves.