Managing Dev Code and Patch Series
These are notes of chatting with Kevin on managing patch in qemu development.
It is a practice that code submitted to qemu are split to small patches, so that they are easy to review. If the code to submit is long, it will be difficult to separate at the end of the development. A better approach is to dev along the will-be series of patch, i.e. when developing a new part create one commit for each patch that will be submitted in the end. Every commit is a logical change, if need to adjust anything on it, we can use rebase command of git.
So the important part to keep handling things easy is that never mix two logically different things in one commit. Changing commits afterwards, or merging them is easy, just splitting is hard.