Re: [ovirt-devel] Stable branch gerrit hook and Related-To: bug

Hi, Let me rephrase your sentence a bit: One commit should contain one self-contained and isolated change. But that does not mean the change is enough to fix the referenced bug. Example: Imagine a situation where you need to add new API to networking part, extend the API in the storage area and then add something new that uses it. Doing this all in a single patch is hard because: 1) All reviewers will have to go through all the code 2) If the development takes time you have to solve conflicts in all the areas all the time On the other hand if you split that into three patches: - Network API improvement (you can go even further and add it call by call where each patch contains new call and relevant test) - Storage API change - New feature Then it is much easier to review. And you can merge the API changes as soon as they are ready and avoid future merge conflicts. Gerrit actually supports this workflow in the form of topic branches. -- Martin Sivák msivak(a)redhat.com Red Hat Czech RHEV-M SLA / Brno, CZ ----- Original Message -----