You can avoid using the –onto parameter by making a temp branch on the commit you like and then use rebase in its simple form:
git branch temp master^
git checkout topic
git rebase temp
git branch -d temp
More Related Contents:
- Insert a commit before the root commit in Git?
- Rebasing a branch including all its children
- Undoing a git rebase
- When do you use Git rebase instead of Git merge?
- Git workflow and rebase vs merge questions
- What is the difference between merge –squash and rebase?
- How to squash all git commits into one?
- What’s the difference between ‘git merge’ and ‘git rebase’?
- Combine the first two commits of a Git repository?
- How to remove/delete a large file from commit history in the Git repository?
- Remove folder and its contents from git/GitHub’s history
- How do I recover/resynchronise after someone pushes a rebase or a reset to a published branch?
- How to rebase many branches (with the same base commit) at once?
- Rebasing a Git merge commit
- Squash the first two commits in Git? [duplicate]
- git pull –rebase lost commits after coworker’s git push –force
- Change old commit message using `git rebase`
- Git interactive rebase without opening the editor
- Git rebase branch with all parent branches (or dependent sub-branches)
- How to retain commit gpg-signature after interactive rebase squashing?
- How to list branches that contain a given commit?
- How can I make git accept a self signed certificate?
- What is a tracking branch?
- I ran into a merge conflict. How do I abort the merge?
- git – skipping specific commits when merging
- How do I get my ‘Detached HEAD’ commits back into master [duplicate]
- Git push rejected “non-fast-forward”
- Get changes from master into branch in Git
- git-svn: what’s the equivalent to `svn switch –relocate`?
- Git merge squash repeatedly