going Posted January 10 Author Share Posted January 10 1 час назад, balbes150 сказал: 15 часов назад, rpardini сказал: What I automated is the boring part, so the human only has to use the eye at the end of it. At least for trivial rebases. It is part of the Python patching system, but only used if invoked manually by a developer. Judging by what I got as a result of building the kernel and studying the log of the patch process, this is not the case. the system interferes with patches and changes them itself, without my permission. the build system should not interfere with patches and break their work. patch processing can be performed exclusively in interactive mode, as a separate function. during the build process, patches should not change in any way. Which of you two should I believe? Here I confirm that the script that analyzes patches, separates them and tries to apply them in parts, as well as the script that will create patches or commit to the code in the source repository should never be called during work the build system itself. Such scripts should be located in the tools folder, they should be called as independent and self-sufficient executable files. 0 Quote Link to comment Share on other sites More sharing options...
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.