Denton Liu <liu.denton@xxxxxxxxx> writes:
>> > I never use the "feature" myself, but I recall that when "git
>> > rebase" is run on a branch appropriately prepared, you do not even
>> > have to say <upstream> (iow, you type "git rebase<RET>" and rebase
>> > on top of @{upstream}).
>> >
>> > Can this new "--keep-base" feature mesh well with it? When the
>> > current branch has forked from origin/master, for example, it would
>> > be good if
>> >
>> > $ git rebase -i --same-base
>> >
>> > becomes a usable short-hand for
>> >
>> > $ git rebase -i --same-base origin/master
>>
>> By "--same-base", I am assuming you mistyped and meant to write
>> "--keep-base"? If that's the case, I can make it a shorthand.
>
> Sorry, I misunderstood your question. "--keep-base" already has the
> shorthand case handled by default.
I actually think you understood _my_ question perfectly well, but
misremembered what your implementation already supported ;-)
If the new option works well with "the branch knows who its upstream
is" feature already, so that the user does not have to type
origin/master in the above example without doing anything special on
your implementation's side, that is a great news.
