Felix Held wrote:
I definitely want to submit a patch train patch by patch and not just the last submittable patches including all patches before to make sure that I looked at each individual patch when submitting.
Maybe the patch train is too long if it becomes hard to keep an overview?
When part of a patch train gets re-pushed due to some small fixes that won't affect patches after a certain patch and then all patches from the patch series are reviewed and submittable, how will the case that later patches are on top of outdated patches be handled?
Hmm, I don't understand what you mean here..
If you have pushed a branch with 3 commits, use interactive rebase locally to fix up the middle commit and then push the branch again, doesn't Gerrit always recognize that the first commit remains unchanged, ie. with one generation less than the middle and last commit?
Previously the latest version of each individual patch was used which is the correct behavior,
If the patches aren't actually linked (ie. can be submitted individually) then I think they shouldn't be pushed as a single branch, right?
//Peter