Re: Usability issue with rebase fork-point option

Robert Dailey writes: > $ git rebase > First, rewinding head to replay your work on top of it... > Applying: Fix state machine hang after integrity checking > > Since my merge-base is already the tip of `origin/master`, I expected > it to say it was up-to-date, as it

Usability issue with rebase fork-point option

When upstream is not specified for the rebase command (e.g. I just do `git rebase`), `--fork-point` is assumed which results in commits regenerating SHA1 even if the merge-base would otherwise be identical. Here's my scenario: I set my remote tracking branch to my parent branch: $ git branch -u