Re: possible completion bug with --set-upstream-to=

2017-12-30 Thread Jeff King
On Sat, Dec 30, 2017 at 09:28:06AM +0100, SZEDER Gábor wrote: > I couldn't reproduce the wrong behavior you saw using v2.1.4 in a > regular setup. > > However, I could reproduce it after I removed the '=' character from > the set of characters in $COMP_WORDBREAKS, but then all completions > afte

Re: possible completion bug with --set-upstream-to=

2017-12-30 Thread SZEDER Gábor
> Whenever I type the last to complete origin/master, as in below: > > > git branch --set-upstream-to=orig > > what I get is: > > > git branch origin/master Yeah, this shouldn't happen. > instead of the expected: > > > git branch --set-upstream-to=origin/master And indeed this is the expe

possible completion bug with --set-upstream-to=

2017-12-29 Thread Ernesto Alfonso
Whenever I type the last to complete origin/master, as in below: > git branch --set-upstream-to=orig what I get is: > git branch origin/master instead of the expected: > git branch --set-upstream-to=origin/master git version and OS: >git version 2.1.4 > >Distributor ID:Debian >Des