author | Shawn O. Pearce <spearce@spearce.org> | |
Thu, 24 May 2007 05:46:49 +0000 (01:46 -0400) | ||
committer | Shawn O. Pearce <spearce@spearce.org> | |
Thu, 24 May 2007 05:46:49 +0000 (01:46 -0400) | ||
commit | fb72759b7de504f077250fd5bd557e3b9e2a5682 | |
tree | 9320c174a6c7cbc8a6d84127d99f55cc6887e434 | tree | snapshot |
parent | c70680ce7cec72a465468c223d43c08f5254d31f | commit | diff |
Teach bash completion about 'git remote update'
Recently the git-remote command grew an update subcommand, which
can be used to execute git-fetch across multiple repositories
in a single step. These can be configured with the 'remotes.*'
configuration options, so we can offer completion for any name that
matches and appears to be useful to git-remote update.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
Recently the git-remote command grew an update subcommand, which
can be used to execute git-fetch across multiple repositories
in a single step. These can be configured with the 'remotes.*'
configuration options, so we can offer completion for any name that
matches and appears to be useful to git-remote update.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
contrib/completion/git-completion.bash | diff | blob | history |