Ralf Thielow <ralf.thielow@xxxxxxxxx> writes: > On Fri, Aug 31, 2012 at 5:22 PM, Carlos Martín Nieto <cmn@xxxxxxxx> wrote: >> Ralf Thielow <ralf.thielow@xxxxxxxxx> writes: >> >>> On Thu, Aug 30, 2012 at 7:23 PM, Carlos Martín Nieto <cmn@xxxxxxxx> wrote: >>>> behaviour. To work around this, introduce --set-upstream-to which >>>> accepts a compulsory argument indicating what the new upstream branch >>>> should be and one optinal argument indicating which branch to change, >>>> defaulting to HEAD. >>>> >>> >>> Could you please also add this new option to the >>> "contrib/completion/git-completion.bash" >>> script? >> >> If I knew how those things work... Is this enough? >> > > Yes, Thanks. While you are at it, perhaps you may want to unadvertise --set-upstream? > >> cmn >> >> --8<-- >> Subject: [PATCH] completion: add --set-upstream-to and --unset-upstream >> >> --- >> contrib/completion/git-completion.bash | 1 + >> 1 file changed, 1 insertion(+) >> >> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash >> index ffedce7..4f46357 100644 >> --- a/contrib/completion/git-completion.bash >> +++ b/contrib/completion/git-completion.bash >> @@ -880,6 +880,7 @@ _git_branch () >> --color --no-color --verbose --abbrev= --no-abbrev >> --track --no-track --contains --merged --no-merged >> --set-upstream --edit-description --list >> + --unset-upstream --set-upstream-to= >> " >> ;; >> *) >> -- >> 1.7.12.3.g0dd8ef6 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html