← Back to context Comment by rkomorn 9 hours ago Isn't your tale more about squashing than rebasing? 4 comments rkomorn Reply OJFord 8 hours ago Any subsequent commits and the branch are inherently rebased on the squashed commit.Rebasing is kind of a short hand for cherry-picking, fixing up, rewording, squashing, dropping, etc. because these things don't make sense in isolation. rkomorn 8 hours ago I guess my point is that I disagree that rebasing should be shorthand for all these things that aren't rebasing. bawolff 8 hours ago Personally i squash using git rebase -i
OJFord 8 hours ago Any subsequent commits and the branch are inherently rebased on the squashed commit.Rebasing is kind of a short hand for cherry-picking, fixing up, rewording, squashing, dropping, etc. because these things don't make sense in isolation. rkomorn 8 hours ago I guess my point is that I disagree that rebasing should be shorthand for all these things that aren't rebasing.
rkomorn 8 hours ago I guess my point is that I disagree that rebasing should be shorthand for all these things that aren't rebasing.
Any subsequent commits and the branch are inherently rebased on the squashed commit.
Rebasing is kind of a short hand for cherry-picking, fixing up, rewording, squashing, dropping, etc. because these things don't make sense in isolation.
I guess my point is that I disagree that rebasing should be shorthand for all these things that aren't rebasing.
Personally i squash using git rebase -i