> rebase keeps the history honest The history is a record of changes. You're suggesting there's a good reason to track timeshifting by implication (you could r

> rebase keeps the history honest The history is a record of changes. You're suggesting there's a good reason to track timeshifting by implication (you could rebase at multiple points) because...honesty? I'm not trying to argue about the why. I'm trying to understand the why. My view is that you merge your change into the head and there's a record. That's the story. The particulars of how a particular commit came to be is irrelevant to the repo and less problematic when it's treated the same as any other commit.