Re: [PATCH] git-completion: offer remotes for 'git remote update'
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 28, 2011, 00:47 UTC
- Message-ID
- <7v8vp9trvu.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <347b845858abcc62551d83df324e5c10@schrijnen.nl>
Auke Schrijnen <auke@schrijnen.nl> writes:
> Completion for 'git remote update' only offers configured remote > groups.
I have this suspicion that it might even be a feature. I am a bad person to make the judgement, as I do not use the "grouping" feature at all.
If you throw in individual remotes that are not grouped in the mix, the users of "git remote update" auto-completion, who have been happily relying on seeing only the configured groups, suddenly will start seeing many individual repositories offered, cluttering the available choices. Besides, if you want to fetch from a single source, why not use "git fetch" directly?
Back when "git fetch" didn't allow fetching from multiple repositories in one go, "remote update" was written as a wrapper for the explicit purpose of fetching from more than one remote by defining remote groups. Since late 2009, "git fetch" can update from multiple remotes itself, and I suspect "git remote update" outlived its usefulness in some sense, but that is a tangent.