| commit | 161fea832a8e8ea7d6cdc1bdc388f19825641a53 | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 24 Jun 2007 23:42:16 +0000 (24 19:42 -0400) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Sun, 24 Jun 2007 23:42:16 +0000 (24 19:42 -0400) | ||
| tree | d6c4d8fd84d6af3e95bcd986d923fd73cb8be7e9 | treesnapshot (tar.gz zip) |
| parent | aeb59328453cd4f438345ea79ff04c96bccbbbb8 | commitdiff |
Teach bash how to complete +refspec on git-push
Using `git push origin +foo` to forcefully overwrite the remote
branch named foo is a common idiom, especially since + is shorter
than the long option --force and can be specified on a per-branch
basis.
We now complete `git push origin +foo` just like we do the standard
`git push origin foo`. The leading + on a branch refspec does not
alter the completion.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Using `git push origin +foo` to forcefully overwrite the remote
branch named foo is a common idiom, especially since + is shorter
than the long option --force and can be specified on a per-branch
basis.
We now complete `git push origin +foo` just like we do the standard
`git push origin foo`. The leading + on a branch refspec does not
alter the completion.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| contrib/completion/git-completion.bash | diffblobblamehistory |