Linus Torvalds writes: (Summary)
But the merges they are are the *only* thing that brings in the new
code, and when you look at history, the code development within one
topic branch is nice and linear and there aren't odd other merges in
the middle.
the middle.
That makes it a *lot* easier to follow a certain strand of development (namely the strand of your topic branch). By definition, the branches you merged were *ready*.
merged were *ready*.
Otherwise you shouldn't have been merging them for an upstream pull request at all!
request at all!
See?
See?
In contrast, the "merge for testing" happens at random times and happens multiple times.
the middle.
That makes it a *lot* easier to follow a certain strand of development (namely the strand of your topic branch). By definition, the branches you merged were *ready*.
merged were *ready*.
Otherwise you shouldn't have been merging them for an upstream pull request at all!
request at all!
See?
See?
In contrast, the "merge for testing" happens at random times and happens multiple times.