Not only it's useful, it's as easy to do in git as typing `git rebase -r`. Recently it even gained support for rewriting branch pointers in the process.
In general, it's almost always better to use long options. So that would be `git rebase --rebase-merges` in this case.
Almost always means: it's better eg when communicating with other humans, whether that's on a forum like HN or in code or scripts. Long options are easier for humans to understand and to 'google'. They also provide some redundancy against typos.
The sole exception, where short options can be useful, is when you are actually using a command line interactively. Use short options to your heart's content there.
Almost always means: it's better eg when communicating with other humans, whether that's on a forum like HN or in code or scripts. Long options are easier for humans to understand and to 'google'. They also provide some redundancy against typos.
The sole exception, where short options can be useful, is when you are actually using a command line interactively. Use short options to your heart's content there.