On Tue, 27 Sep 2011 17:47:17 -0700, Junio C Hamano wrote:
Auke Schrijnen <auke@xxxxxxxxxxxx> 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.
I see your point and obviously i'm also not using the grouping feature.
I could just use git fetch but i'm so used to type 'git remote
update'... So i'll cook another patch.
Auke
--
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