Re: Using two-dot range notation in `git rebase`?

> Jeff King <peff@peff.net> writes:
> 
> > long as there is only one negative tip given, that becomes the "--onto"
> > point).
> 
> So "git newbase [--options] A..B" would
> 
>  - checks if B names an existing branch or just a commit
> 
>  - detaches HEAD at commit A
> 
>  - replays commits in DAG A..B on top of it; the exact way the
>    history is replayed is affected by the options given (e.g. "-m"
>    and "-p" may try to preserve history shapes)
> 
>  - if B was determined to be a branch name, "git branch -f" to it;
>    otherwise leave the HEAD detached.
> 
> which all sounds OK, but I do not see a huge improvement over the
> current "git rebase [--options] A B" (other than that you can type
> double dot instead of a single space).